Feature add no force option rule #47
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mskelton
reviewed
Apr 23, 2022
| @@ -22,6 +23,7 @@ module.exports = { | |||
| "playwright/no-focused-test": "error", | |||
| "playwright/no-skipped-test": "warn", | |||
| "playwright/no-wait-for-timeout": "warn", | |||
| "playwright/no-force-option": "warn", | |||
There was a problem hiding this comment.
This one, I'm not sure about for the default rules, I can see both sides. @mxschmitt Thoughts?
There was a problem hiding this comment.
usually you never have to use force. Only when Playwright has bugs or the application which you are testing does not follow the accessibility standards. So I'd vote for emitting a warning, if users scream, we can change it anyway or they disable the rule manually.
…nt-plugin-playwright into feature-add-no-force-option-rule
mxschmitt
approved these changes
Apr 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#43