Rule to disallow some arg names that were meant for attribute bindings
See original GitHub issueA rule to disallow @class
and @classNames
and other attribute binding arguments would be good, especially for angle bracket invocations. I am converting some curly component invocations to angle brackets and want to take the conversion to ...attributes
in a separate pass.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Python Scope & the LEGB Rule: Resolving Names in Your Code
In this step-by-step tutorial, you'll learn what scopes are, how they work, and how to use them effectively to avoid name collisions in...
Read more >Chapter 5. The Rule Language - JBoss.org
Attributes are simple (always optional) hints to how the rule should behave. LHS is the conditional parts of the rule, which follows a...
Read more >match.arg: Argument Verification Using Partial Matching - Rdrr.io
In the one-argument form match.arg(arg) , the choices are obtained from a default ... one unless several.ok is TRUE ' rule, and returns...
Read more >Binding with let, use, and do | F# for fun and profit
One is to define a named expression at a the top level of a module*, and the other is to define a local...
Read more >Chapter 6. Aspect Oriented Programming with Spring
There are some things you cannot do easily or efficiently with Spring AOP, ... compiler (ajc) then there is no need to add...
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
Personally, I mostly care about
@classNames
,@alt
,@role
and@data-test-*
. that’s probably 95% of my use cases.but it will be moot pretty soon since we’re almost fully converted to glimmer components.
I think part of that convo pointed out that we could split that work into separate PR’s:
onclick=
style attributes (across the board)I think the issues that I was pointing out was with the latter part, I think the first (rule preventing
onclick=
) would be something we could move on a bit easier while we figure out the second.