Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

__ and __n function naming #34

Closed
eliOcs opened this issue Sep 17, 2012 · 2 comments
Closed

__ and __n function naming #34

eliOcs opened this issue Sep 17, 2012 · 2 comments

Comments

@eliOcs
Copy link

eliOcs commented Sep 17, 2012

__ and __n may be a common syntax but they are not expressive. Configuration options should be included to choose other names.
This would also help with the conflict with the jade internals.

@mashpie
Copy link
Owner

mashpie commented Dec 7, 2012

in either way, you may register them with your own mappings, like you'd do for helpers:

// register helpers for use in templates app.helpers({ __i: i18n.__, __n: i18n.__n });

@eliOcs
Copy link
Author

eliOcs commented Dec 7, 2012

It's true defining helpers allows you to change the names anyway. Thanks.

@eliOcs eliOcs closed this as completed Dec 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants