-
-
Notifications
You must be signed in to change notification settings - Fork 929
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
Add --rule
flag, --rules
flag, --merge-rules
flag and mergeRules
option
#7252
Conversation
🦋 Changeset detectedLatest commit: 61e9858 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
892760b
to
a624ce2
Compare
ade7316
to
61e9858
Compare
--rule
flag, --merge-rules
flag and mergeRules
option
@Mouvedia Can you please wait until the |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@Mouvedia You can restart this. But I'm concerned about where the |
--rule
flag, --merge-rules
flag and mergeRules
option--rule
flag, --rules
flag, --merge-rules
flag and mergeRules
option
Closed in favour of #7418. |
#4331
levn has limited uses; I could refactor and use
JSON.parse
instead.e.g. having a schema for an object requires explicit property names
missing features
Passing a rule without its value seemed confusing.
What should
--rule color-no-invalid-hex
do exactly?Probably fetch the corresponding rule option in the config and, if found, discard all other rules.
I chose not to add this feature, for now; it needs to be discussed in a separate issue.
--rules
should accept a file path (JSON)