Fix conflicting formatting by using prettier for everything #33
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
castrodd
approved these changes
Feb 6, 2024
This was referenced Feb 6, 2024
Fix conflicting formatting by using prettier for everything
Azure/azure-functions-nodejs-library#218
Merged
Merged
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.
Related to conversation here: #32 (comment)
We use prettier for TypeScript files but the default formatter from VS Code (whatever that is) for other file types. This PR makes it so that we use prettier for all files, which should prevent any conflicts.
I split this into two commits, the first modifies the settings and the second formats all files.