-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Inconsistency between api doc and implementation #1237
Comments
I'm pretty sure that it's due to backwards-compatibility with Mustache. It also accepts |
blikblum
added a commit
to blikblum/handlebars.js
that referenced
this issue
Jul 21, 2016
As pointed in handlebars-lang#1237 BlockStatement.path accepts in practice PathExpression or Literal. Updates its definition to reflect this fact
nknapp
pushed a commit
that referenced
this issue
Mar 9, 2017
As pointed in #1237 BlockStatement.path accepts in practice PathExpression or Literal. Updates its definition to reflect this fact
We need a spec #1277 |
The documentation has actually been updated in 8088a46. Closing |
This was referenced Sep 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using the compiler API and the specs as references to port handlebars to pascal
The API states that BlockStatement path must be a PathExpression but the parser accepts string,number and even boolean literals in path.
The examples below works:
The current implementation gives the expected behavior and the doc is misleading?
The text was updated successfully, but these errors were encountered: