-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
inconsistent behavior of filter pulling from context based on name #140
Comments
Michael Bayer (@zzzeek) wrote: the issue is because we consider the identifier 'h' to be declared at parse tree time. the ${'foo' | h, h.strip} I suppose the fix to that would be, because h.strip is there, its undeclared. "h" as a builtin would basically be blown away from that. the other solution is, don't allow "h.strip" in there. if we work with the regexp in codegen create_filter_callable(), we could have that. It's probably preferable. |
Changes by Michael Bayer (@zzzeek):
|
Changes by Michael Bayer (@zzzeek):
|
Changes by Michael Bayer (@zzzeek):
|
cocolato has proposed a fix for this issue in the main branch: Support passing custom filters with the same name as built-in flags https://gerrit.sqlalchemy.org/c/sqlalchemy/mako/+/5557 |
1.3.7 is yanked. a test + yank is added in https://gerrit.sqlalchemy.org/c/sqlalchemy/mako/+/5579 |
add new tests that use 'n' as a default filter argument and ensure 'n' takes effect when used in this way |
I will try this again. |
Migrated issue, originally created by Michael Bayer (@zzzeek)
this is related to #3 but seems different
The text was updated successfully, but these errors were encountered: