WRR-1011: Fixed storybook-utils eslint and prettier lint rules to not conflict
#91
Conversation
This file contains 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
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.
Checklist
Issue Resolved / Feature Added
Storybook-utils's
eslintrules andprettierlint rules are opposite for applying spacing after function keyword. Currently a workaround was applied to avoid the conflicts.Resolution
I have reverted the code before the workaround intended to avoid lint warnings. The fix will be applied in enactjs/eslint-config-enact#93.
Additional Considerations
Links
WRR-1011
Comments
Enact-DCO-1.0-Signed-off-by: Stanca Pop [email protected]