Can't use $ as an attribute name
See original GitHub issueI sometimes prefix my attributes with $
, as $amount
. Then, when using it on my templates, I get the following error:
emblem/parser.js:7689
throw peg$buildException(null, peg$maxFailExpected, peg$maxFailPos);
^
SyntaxError: Expected _4BeginStatement or end of input but "\uEFEF" found.
Example code:
div= transaction.$amount
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Attribute name not allowed on element div at this point
I found some entry from: Markup Validation Error: "Attribute name not allowed on element at this point" error #HTML5.
Read more >Attribute '<attributename>' cannot be applied multiple times
The attribute can only be applied once. The AttributeUsage attribute determines whether an attribute can be applied more than once. Error ID: ...
Read more >How to Access an Object Attribute Given the Attribute Name as ...
You first create a Gun class object. Second, you get its caliber and color. Since your object does not have an attribute called...
Read more >lightning aura components - cant set attribute of type object
This is because you have declared, beerList in Aura as Object . If you are passing List from backend then declare that as...
Read more >Expression attribute names in DynamoDB - AWS Documentation
An expression attribute name is a placeholder that you use in an Amazon DynamoDB expression as an alternative to an actual attribute name....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@tmosmant I’ll look soon for a fix, it looks like a parser bug
I’m not 100% sure, but I suspect this may be a good place to start.