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

Why can't use 'msg' as template variable name? #62

Open
dxvgef opened this issue May 30, 2017 · 2 comments
Open

Why can't use 'msg' as template variable name? #62

dxvgef opened this issue May 30, 2017 · 2 comments

Comments

@dxvgef
Copy link

dxvgef commented May 30, 2017

If use 'msg' as template variable name, will appear this error:
unexpected token <msg> on operand

annismckenzie added a commit that referenced this issue May 31, 2017
@annismckenzie
Copy link
Member

Looked into the source briefly – looks like msg is an identifier in the lexer but if I read this correctly, it isn't used yet. It is supposed to be used for translating messages (right, @jhsx?). I pushed a new branch with a failing test case.
For a possible fix, I'm gonna have to defer this one to @jhsx.

@jhsx
Copy link
Member

jhsx commented Jun 1, 2017

Hi, you're correct, the idea was to add msg statement as the example,

<b>{{msg "myKey"}}Default Value{{end}}</b>

But after think more i'm considering to add internationalization support as a sub project, without a new type of statement, i will open an describing issue soon.

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

3 participants