option to apply filters before the defaults ?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 459
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
Migrated issue, originally created by Anonymous
Maybe I am wrong here, but shouldn't default filters such as unicode() be applied last? The fact that it's done the exactly opposite way makes it a pain, as we are limited to deal with the string/unicode representation of whatever variable is passed to the filter.
Hence, I propose the following change:
diff -r 29d9a098a70465450563e9c07ed613e227886936 mako/codegen.py
--- a/mako/codegen.py Fri Aug 05 17:45:51 2011 -0400
+++ b/mako/codegen.py Mon Aug 08 11:14:48 2011 +0200
@@ -669,7 +669,7 @@
if self.compiler.pagetag:
args = self.compiler.pagetag.filter_args.args + args
if self.compiler.default_filters:
- args = self.compiler.default_filters + args
+ args = args + self.compiler.default_filters
for e in args:
# if filter given as a function, get just the identifier portion
if e == 'n':
What do you think?
Cheers,
Pedro
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in mako/codegen.py at the default_filters branch shown in the issue and review the comment discussion to clarify whether ordering should always change or be optional. Verify the resulting filter order for explicit and default filters, and ensure the behavior is covered by the relevant existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100