docs(oxfmt): Include links for the VS Code extension in the formatter FAQ #658
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
… FAQ Lead with the VS Code extension since that's the best route for many users. Also rephrase the wording slightly. Signed-off-by: Connor Shea <[email protected]>
✅ Deploy Preview for oxc-project ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
leaysgur
approved these changes
Nov 26, 2025
Member
leaysgur
left a comment
leaysgur
left a comment
There was a problem hiding this comment.
I think the content is good. 👌🏻
However, in fact, as of this very moment, I understand that the VSCode extension does not yet support oxfmt. 🙈
Contributor
Author
Good point! We can probably hold off on this change for a few days if we want to. |
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.
Lead with the VS Code extension in the answer, since that's the best and main officially-supported route for many users. Also rephrase the wording slightly.
We should maybe also note that the user will need to enable the formatter via a setting in the VS Code extension? Unless we intend to remove that step in the very near future.