You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently filters are only provided as a render option, which prevents us from checking if a filter call is valid during parsing and providing faster feedback about a bug in a template.
Also, we would like to use information about what filters will be available, along with what parameters they take, in liquid-c. That will allow us to skip render time checks to see if a filter is invokable and avoid the need to translate ArgumentError exceptions to Liquid::ArgumentError from passing in the wrong number of arguments.
The text was updated successfully, but these errors were encountered:
Currently filters are only provided as a render option, which prevents us from checking if a filter call is valid during parsing and providing faster feedback about a bug in a template.
Also, we would like to use information about what filters will be available, along with what parameters they take, in liquid-c. That will allow us to skip render time checks to see if a filter is invokable and avoid the need to translate ArgumentError exceptions to Liquid::ArgumentError from passing in the wrong number of arguments.
The text was updated successfully, but these errors were encountered: