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
{{ message }}
This repository has been archived by the owner on Dec 3, 2018. It is now read-only.
I think it's more consistent to rename twig functions to snake_case naming convention: getWebpackCssFiles -> webpack_css_files getWebpackJsFiles -> webpack_js_files
And instead of two additional functions renderWebpack*Tags I recommend using templates:
I think it's more consistent to rename twig functions to snake_case naming convention:
Hmm, you're right about that!
And instead of two additional functions renderWebpack*Tags I recommend using templates:
That's WAY more work, and the arguments (options in this case) are way less discoverable. But, we could actually create these templates, and have the renderWebpack*Tags() use them internally.
I think it's more consistent to rename twig functions to snake_case naming convention:
getWebpackCssFiles
->webpack_css_files
getWebpackJsFiles
->webpack_js_files
And instead of two additional functions
renderWebpack*Tags
I recommend using templates:The text was updated successfully, but these errors were encountered: