You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's why buns new text lock file is a JsonC file which is JSON with support for comments and trailing commas. This makes it much easier to view diffs and pull requests and trailing commas make it much less likely to cause merge conflicts.
The text was updated successfully, but these errors were encountered:
I'm personally very much pro trailing comma. I know some members of the team are against them for reasons I cannot understand, I don't know where the numbers sit on how many are for and against.
I'm in the anti trailing comma camp. It looks nicer and consistently works in all file formats. I didn't have anything to do with it being set to none and don't know how it originally was decided, but I guess that must means there's at least some other folks out there who prefer not to have it
Is there a reason why
"trailingComma": "none"
is set in the template?es5
toall
in v3.0.0Quote from the Bun 1.2 changelog:
The text was updated successfully, but these errors were encountered: