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

Error instead of warn when no features are selected. #643

Merged
merged 1 commit into from
Jan 29, 2018

Conversation

mbleigh
Copy link
Contributor

@mbleigh mbleigh commented Jan 29, 2018

We have gotten questions on a regular basis to the effect of "I deployed, but nothing happened" that turned out to be confusion after initializing without selecting any features.

I think it will be a better beginner experience if we explicitly error out in this case rather than printing an easy-to-miss warning message and continuing with initialization.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 57.502% when pulling 0c95a36 on mb-nofeature-err into 583febd on master.

1 similar comment
@coveralls
Copy link

coveralls commented Jan 29, 2018

Coverage Status

Coverage remained the same at 57.502% when pulling 0c95a36 on mb-nofeature-err into 583febd on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants