Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When the user provides eslint.options, remove the requirement for a eslint.config.js file #1859

Open
John-Dean opened this issue Jun 10, 2024 · 1 comment
Labels
feature-request Request for new features or functionality
Milestone

Comments

@John-Dean
Copy link

Hello,

In my VSCode settings.json I have the following:

	"eslint.options": {
		"baseConfig": {
			"rules": {
				...RULES HERE
			}
		}
	}

When I format with eslint these are added to my eslint.config.js file.

However, the file still needs to exist somewhere for this to work.

Can we add a mode that only uses the eslint.options as the config file if it doesn't exist? i.e. If the config file can not be found, make an empty one and then proceed using an empty file in combination with "eslint.options".

At the moment I know this works as I have put a dummy config file in my C: directory which is completely empty, but if I remove this file eslint refuses to format.

Thanks,
John

@dbaeumer dbaeumer added the feature-request Request for new features or functionality label Jun 11, 2024
@dbaeumer dbaeumer added this to the Backlog milestone Jun 11, 2024
@dbaeumer
Copy link
Member

I am not really convinced since this is something eslint itself expects and nothing the extension enforces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants