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

Fix: Do not throw exception if baseConfig is provided (fixes #6605) #6625

Merged
merged 1 commit into from Jul 8, 2016

Conversation

platinumazure
Copy link
Member

What issue does this pull request address?

When using CLIEngine, specifying baseConfig was not enough to prevent a No Config Found exception from being thrown. This change will ensure that no exception is thrown if baseConfig is provided to CLIEngine.

What changes did you make? (Give an overview)

Check if baseConfig is present in lib/config.js before throwing an exception, plus test, plus change to migration guide.

Is there anything you'd like reviewers to focus on?

Not 100% sure if baseConfig should be checked for at least one key, like "rules" is. Assumption is that baseConfig is null/undefined by default, and so an empty object still represents a conscious user decision to provide a config (even if empty). If this is a bad assumption, let me know.

@eslintbot
Copy link

LGTM

@gyandeeps
Copy link
Member

LGTM 👍
Thanks for contributing.

@gyandeeps gyandeeps merged commit 2bdf22c into eslint:master Jul 8, 2016
@platinumazure platinumazure deleted the allow-baseconfig branch March 20, 2017 18:05
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 6, 2018
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Feb 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants