Added support of custom template filters #49
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was an issue with using this project with generated models.
I have the following section in my custom-data.js file:
These getter methods weren't correctly exported to the resulting Role model because of unthoughtfully working 'stringifyIfObject' filter: it returned an empty object or a string in different variations of getter methods.
So I decided to add an ability to create own template filters inside of 'util/template-filter.js' file of the template folder (not the pg-generator folder!).
This pull request adds new nunjucks filters and makes them available for use with model generating template.
As for me, this new filter totally fixed the issue with getter methods:
So the following change in 'table/definition/{table.name # dashCase}.js.nunj.html' totally fixed the issue using the newly created filter:
How to use
Simply add a 'template-filter.js' file into the 'util' subdirectory of your template folder and write the code just as following:
And then you can use the new filter in your templates: