feat(oxfmt): More friendly JSON schema #14879
Merged
+369
−95
Conversation
This file contains hidden or 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
github-actions
bot
added
A-formatter
Member
Author
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
CodSpeed Performance ReportMerging #14879 will not alter performanceComparing Summary
Footnotes
|
Dunqing
approved these changes
Oct 22, 2025
leaysgur
force-pushed
the
10-22-feat_oxfmt_support_ignorepatterns_in_oxfmtrc
branch
from
24d08d4 to
43867d3
Compare
leaysgur
force-pushed
the
10-22-feat_oxfmt_more_friendly_json_schema
branch
from
229b2be to
5442349
Compare
Contributor
Merge activity
|
It now shows the description and the specific string value.
graphite-app
bot
force-pushed
the
10-22-feat_oxfmt_support_ignorepatterns_in_oxfmtrc
branch
from
43867d3 to
006708d
Compare
graphite-app
bot
force-pushed
the
10-22-feat_oxfmt_more_friendly_json_schema
branch
from
5442349 to
381e08c
Compare
Base automatically changed from
10-22-feat_oxfmt_support_ignorepatterns_in_oxfmtrc
to
main
October 22, 2025 08:30
graphite-app
bot
deleted the
10-22-feat_oxfmt_more_friendly_json_schema
branch
graphite-app bot
pushed a commit
that referenced
this pull request
Oct 22, 2025
## [0.8.0] - 2025-10-22 ### 🚀 Features - 381e08c oxfmt: More friendly JSON schema (#14879) (leaysgur) - 006708d oxfmt: Support `ignorePatterns` in oxfmtrc (#14875) (leaysgur) ### 🐛 Bug Fixes - 64b8226 formatter: Corrct printing leading own line comments before method body (#14886) (Dunqing) - 6ce1162 formatter: Remove a redundant space for TSMappedType (#14885) (Dunqing) - 5b962a7 formatter: Remove redundant leading space when only the rest part of the array exists (#14884) (Dunqing) - 8301d8f formatter: No need to wrap parenthesis for ObjectExpression when it is an expression of a template literal (#14883) (Dunqing) - 9397472 formatter: Should not wrap parenthesis for ComputedMemberExpression when it is not an option or it doesn't contain a call expression (#14882) (Dunqing) - 3e62277 formatter: Should not add a soft line for the arrow function inside ExpressionContainer with a trailing comment (#14878) (Dunqing) - 990916a formatter: Correct handling of leading own line before arrow function body (#14877) (Dunqing) - 4a499b5 formatter: Correct printing trailing comments for if statement with non-block consequent (#14857) (Dunqing) ### 🧪 Testing - 868ff99 formatter: Fix tests using TS syntax with `.js` (#14880) (leaysgur)
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.
It now shows the description and the specific string value.