[GH-ISSUE #855] 80 or 85 print width formatting #185

Closed
opened 2026-05-06 12:37:57 +02:00 by BreizhHardware · 3 comments

Originally created by @NathanDrake2406 on GitHub (Apr 16, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/855

It's a lot more tasteful and pleasant to the eye

Originally created by @NathanDrake2406 on GitHub (Apr 16, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/855 It's a lot more tasteful and pleasant to the eye
Author
Owner

@james-elicx commented on GitHub (Apr 17, 2026):

I'm afraid these things come down to personal preference, and I often lean towards a larger print width.

I generally agree with oxfmt's default of 100.

It would be nice if we had tooling that worked seamlessly with supporting individuals having their own formatting config locally, and a different one when pushed to a branch...

<!-- gh-comment-id:4266111152 --> @james-elicx commented on GitHub (Apr 17, 2026): I'm afraid these things come down to personal preference, and I often lean towards a larger print width. I generally agree with oxfmt's [default](https://oxc.rs/docs/guide/usage/formatter/config-file-reference.html#printwidth) of 100. It would be nice if we had tooling that worked seamlessly with supporting individuals having their own formatting config locally, and a different one when pushed to a branch...
Author
Owner

@NathanDrake2406 commented on GitHub (Apr 17, 2026):

I'm afraid these things come down to personal preference, and I often lean towards a larger print width.

I generally agree with oxfmt's default of 100.

It would be nice if we had tooling that worked seamlessly with supporting individuals having their own formatting config locally, and a different one when pushed to a branch...

Wow. I’ve never been this upset in my life

<!-- gh-comment-id:4266460032 --> @NathanDrake2406 commented on GitHub (Apr 17, 2026): > I'm afraid these things come down to personal preference, and I often lean towards a larger print width. > > I generally agree with oxfmt's [default](https://oxc.rs/docs/guide/usage/formatter/config-file-reference.html#printwidth) of 100. > > It would be nice if we had tooling that worked seamlessly with supporting individuals having their own formatting config locally, and a different one when pushed to a branch... Wow. I’ve never been this upset in my life
Author
Owner

@james-elicx commented on GitHub (Apr 17, 2026):

😢

<!-- gh-comment-id:4266475321 --> @james-elicx commented on GitHub (Apr 17, 2026): 😢
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vinext#185
No description provided.