docs: fix Zed Oxc configuration - #2592
Open
joschuba wants to merge 5 commits into
Open
Conversation
✅ Deploy Preview for viteplus-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
fengmk2
reviewed
Sep 1, 2026
fengmk2
approved these changes
Sep 3, 2026
fengmk2
changed the title
Member
|
@joschuba Thanks, I will fix format issue before merge. |
Signed-off-by: Johannes Schuba <hi@joschuba.digital>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix the Zed configuration example so source.fixAll.oxc is configured as a formatter code action instead of an invalid language-level setting. The Oxc Zed example configuration is doing it the same way: oxc-project/oxc-zed example configuration
Also add JSX and TSX, since Zed treats them as separate languages and the TypeScript/JavaScript formatter settings don't apply to them. This tripped me up while setting up the integration just now, since my TSX files were still being formatted with the default settings.