Skip to content

Conversation

@susnux
Copy link
Contributor

@susnux susnux commented Sep 23, 2025

Added new configuration options for disabling linting or formatting and made all configurations aware of it.
To make use of it the createConfig method is exposed now for advanced use cases.

@susnux susnux requested a review from ShGKme September 23, 2025 13:08
@susnux susnux added enhancement New feature or request 3. to review labels Sep 23, 2025
@susnux
Copy link
Contributor Author

susnux commented Sep 25, 2025

@ShGKme was this what you were asking for?

Copy link
Contributor

@ShGKme ShGKme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was this what you were asking for?

Yes, but it is not available initially. You need to create the config, right? We do not provide it pre-created.

…teConfig`

Added new configuration options for disabling linting or formatting and
made all configurations aware of it.
To make use of it the `createConfig` method is exposed now for advanced
use cases.

Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
@susnux
Copy link
Contributor Author

susnux commented Oct 15, 2025

I am still not really convinced this is the right approach. IMHO for a consistent ecosystem we should enforce one tool with consistent rules for all. Meaning using ESLint and once we decide to switch to oxc as a linter then we should do so by providing a config that all products use and deprecate eslint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[feat] Split config into linting and formatting

3 participants