oxfmt: Support format options

[leaysgur]

Various CLI options like:

• --print-width
• --trailing-comma
• etc...

https://prettier.io/docs/options

We will also consider whether these are necessary in the first place.

[Sysix]

Defining a useful option in CLI but not in the config file, requires the language server to define an own option for it.
Prettier recommends using the config file for syncing the different tools:
https://github.com/prettier/prettier-vscode?tab=readme-ov-file#configuration

Using Prettier Configuration files to set formatting options is the recommended approach.

Just wanted to drop it here 🫶

[leaysgur]

Thanks~!

Of course we support configuration files, but this was intended as an additional CLI argument.
(The priority may be lowered, or it may be reconsidered later.)

[PointSingularity]

Does the current release (0.2.0) support any config at this point (file based one), or is that yet to come?

[lisiur]

I really appreciate your efforts, and I'm looking forward to the implementation of stdin. This way, it can be immediately integrated into editors like nvim or helix. As a result, we can start using it right away in real coding environments and provide timely feedback.

[leaysgur]

Does the current release (0.2.0) support any config at this point (file based one), or is that yet to come?

Yes, there is currently no support for config(file, cli flags), ignore, etc... yet. 😅

Please watch individual issue for that. #13611

I'm looking forward to the implementation of stdin.

#13608 is the right place to hear your voice~. 👍🏻

[KieranP]

I would recommend against implementing dozens of CLI flags.

In my view, it would be better to encourage people to use the config files:

oxfmt # .oxfmtrc.json by default
oxfmt --config=lint.json

Or if it must be in the CLI, option to provide JSON like this:

oxfmt --config='{ "trailingComma": "es5" }'

[leaysgur]

oxfmt # .oxfmtrc.json by default
oxfmt --config=lint.json

This is now supported by #14398. 🎉

oxfmt --config='{ "trailingComma": "es5" }'

I'm also leaning towards this approach rather than implementing a lot of option flags.

I'll close this issue for now, but I'll revisit it based on feedback.