-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[New] forbid-dom-props: Add disallowedValues
option for forbidden props
#3877
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3877 +/- ##
==========================================
+ Coverage 97.64% 97.66% +0.02%
==========================================
Files 133 136 +3
Lines 9966 9986 +20
Branches 3703 3706 +3
==========================================
+ Hits 9731 9753 +22
+ Misses 235 233 -2 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using a regex is a nonstarter; see #3876 (comment)
a7911e2
to
d52c0f1
Compare
de2e1ea
to
5d3d27c
Compare
valueRegex
option for forbidden propsdisallowedValues
option for forbidden props
I changed |
@ljharb, hello! Opensource is practically new to me. Could you please guide me on this PR's flow? When can it be merged? |
Add
disallowedValues
for disallowing only certain values for certain propsDiscussion: #3876