Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Angle braket components trigger no-quoteless-attributes
See original GitHub issue<MyComponent @attr=true/>
However this is not an HTML attribute, so I guess this is a bug.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Angle Bracket Invocation for Nested Components (3.10)
With angle bracket syntax, we use the @ at sign to distinguish JavaScript data from HTML attributes. No more attribute bindings, and improved...
Read more >Templates - Octane Upgrade Guide - Ember Guides
With angle brackets, since you can pass standard HTML attributes to the component directly, we need a way to distinguish between those and...
Read more >Ember Templates: Classic vs Angle Bracket Syntaxes - Salsify
Diving into the difference between Ember component invocation when using curlies, angle brackets, and s-expression in Ember templates.
Read more >Angle bracket (<) without triggering html code - Stack Overflow
The character “<” is the LESS THAN character. If you actually meant an angle bracket, then you can use U+2329 LEFT-POINTING ANGLE BRACKET...
Read more >Pass attributes to glimmer components when using ... - GitHub
With angle brackets and the distinction between arguments and attributes it is no longer possible to pass down attributes to those components.
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 Free
Top 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
IMHO, it’s a good thing, in your example @jkubaile you are passing the string “model” not the current value of
{{model}}!No, this is exactly the scenario we are trying to catch. In your template you will be passing the string “true” as an argument. This is almost never what you actually want (and is confusing to most people) so we created the rule to enforce quotes so that it becomes much clearer what is happening. If you want to pass a Boolean value you would do
@foo{{true}}…