Skip to content

Format Code - prettier #790

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

Merged
merged 7 commits into from
May 2, 2023
Merged

Format Code - prettier #790

merged 7 commits into from
May 2, 2023

Conversation

AliyanH
Copy link
Member

@AliyanH AliyanH commented Mar 13, 2023

created a new grunt task (to replace the 'test' grunt task) to format code using prettier.
One of the code formats (Conditional ternary operator) performed by prettier seems to cause errors with jshint - maybe jshint is not needed anymore when we use a code formatter.

Seems to format code nicely, though we can finetune it as needed also - https://prettier.io/docs/en/options.html

resolves #773.

@AliyanH AliyanH marked this pull request as ready for review May 1, 2023 20:13
@AliyanH AliyanH requested a review from prushforth May 1, 2023 20:13
Copy link
Member

@prushforth prushforth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Once we squash and merge, we can add a .git-blame-ignore-revs file to the root folder, containing the commit hash of the squashed commit. We also have to remember to document that new devs should use the following command to ignore this particular commit, permanently:

 git config --global blame.ignoreRevsFile .git-blame-ignore-revs

@AliyanH AliyanH merged commit 12dcdf7 into Maps4HTML:main May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Select a code formatter and implement in build step
2 participants