-
Notifications
You must be signed in to change notification settings - Fork 612
chore: switch to prettier@2 defaults with 120 printWidth #1185
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
chore: switch to prettier@2 defaults with 120 printWidth #1185
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this 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!
a663ebb
to
ebcf028
Compare
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 again
If anyone is visiting this PR in future. Discussions related to printWidth: [May 14, 2020, 12:08 PM] Kamat, Trivikram: I use 27-inch 4K monitor at home, and use Spectacle to use 66% of width for VSCode editor
I added editor.rulers for [80, 100, 120], and ruler for 120 doesn’t appear for default font-size (needs horizontal scrolling)
[May 14, 2020, 12:08 PM] Kamat, Trivikram: ☝️ that’s why I’m inclined to printWidth 100
But I’m open to change my mind if 120 printWidth is more helpful for you folks.
[May 14, 2020, 12:16 PM] Forsyth, Alex: 100 vs 120. 120 looks so much better
[May 14, 2020, 12:21 PM] Kamat, Trivikram: I’m open to both 100 and 120, but would prefer to vote for 100
Let’s finalize whichever Allan like, and stick with it.
[May 14, 2020, 12:23 PM] Kamat, Trivikram: These are all the prettier configurations https://prettier.io/docs/en/options.html
My recommendation is to remove prettier v1 default configs which we’d currently set https://github.com/aws/aws-sdk-js-v3/blob/117e9ca7b11b9dc0614a6af5eca90b44e7673ac2/.prettierrc#L3-L5
[May 14, 2020, 12:25 PM] Zheng, Allan: If Both Trivikram and me don’t have a stance, let use 120 width then
[May 14, 2020, 12:26 PM] Kamat, Trivikram: 120 it is! 🎉 Discussions related to decision: [May 14, 2020, 12:30 PM] Kamat, Trivikram: If you don’t have a stance, I’ll remove the prettier@1 defaults. But will wait for your response.
[May 14, 2020, 12:32 PM] Forsyth, Alex: Personally dont care.
[May 14, 2020, 12:32 PM] Zheng, Allan: Yea if we decide to do a huge reformating this time, lets do every change we want
[May 14, 2020, 12:33 PM] Kamat, Trivikram: Cool! I’ll remove the prettier@v1 defaults
[May 14, 2020, 12:33 PM] Zheng, Allan: Similarly, we need to keep the config entries to make sure it won’t change when prettier prefers other format next time |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Issue #, if available:
Follow-up to #1183
Description of changes:
switch to prettier@2 defaults with 120 printWidth
Verified that vscode-prettier formats the page on edit
Screen recording
prettier-vscode Output
Verified that yarn generate-clients use printWidth 120 on CodeGen code
diff
Verified that husky formats files with printWidth 120 on precommit
terminal output
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.