Feature linter formatter #72
Open
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
… venv to avoid dependency conflicts
…ity and applied the rules of them to the files
…h to resolve next/babel to avoid errors
…s, removed unused dependencies
|
@joemccann @Anil-matcha @staeiou Heyo, would be appreciated if anybody can have a look on this. |
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.
I extended the functionality of next lint and added stylelint to lint css. The stylelint rules are mostly a merge of the stylelint-config-standard and stylelint-config-recommended rules. I know every coder has its own style, so feel free to adjust some rules, if you don't like them.
Moreover, I updated the README to use a venv to avoid dependency conflicts (which I got without it) and added source_documents to the .gitignore file.
Additionally, I cleaned up the requirements.txt file using pipreqs.