feat(oxfmt): Add --config-field CLI option

[leaysgur]

NOTE: I'd like to merge this in sync with oxlint.

[leaysgur]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(oxfmt): Add --config-field CLI option #20138 👈 (View in Graphite)
• feat(oxfmt): .js/.ts config file support #20135 : 1 other dependent PR (#20197 )
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent changes, fast-track this PR to the front of 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.

[Sysix]

I would like to have a intergration test for it. We created a similar js test setup for oxlint lsp :)

[camc314]

How is the LSP going to invoke this? Does it bypass the vscode extension? or some other way?

What about for non-vscode users? Do they manually have to configure this in the LS config?

[Sysix]

@camc314 every client (IDE/editor) is responsible to configure the new configuration like the CLI.
For VS Code @leaysgur already created a PR oxc-project/oxc-vscode#134.
This allows to define VS Code settings and pass it to the language server.
Example zed: https://github.com/oxc-project/oxc-zed/blob/main/examples/oxlint/nested-configs/.zed/settings.json

[camc314]

hmm @leaysgur shall we discuss this tomorow? I think we want this to be as low-friction as possible for vite+, and requireing a user to configure this doens't feel ideal

[leaysgur]

@Sysix Thanks~! Once it's merged, I'd like to add some tests soon. 👀

@camc314 Of course. (Since there's been ongoing discussion since last week, it might be best to first review the Discord and VP-side issues as well.)

[leaysgur]

We've decided to take a different approach, so closing.