#3 Migrate to ESlint and code formatting using prettier and husky #13
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
oubchid
force-pushed
the
jmap_ts-3-migrate-to-eslint-code-formatting
branch
3 times, most recently
from
c4e0655
to
d10865e
Compare
oubchid
changed the title
oubchid
force-pushed
the
jmap_ts-3-migrate-to-eslint-code-formatting
branch
from
8ffc7c3
to
1bbf0ef
Compare
alagane
approved these changes
Jan 14, 2021
oubchid
force-pushed
the
jmap_ts-3-migrate-to-eslint-code-formatting
branch
from
1bbf0ef
to
99a14a0
Compare
oubchid
force-pushed
the
jmap_ts-3-migrate-to-eslint-code-formatting
branch
from
99a14a0
to
3bfa8db
Compare
Closed
rezk2ll
approved these changes
Jan 19, 2021
Closed
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.
example
pre-pushhook