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

Add a way to identify possible misconfigurations #17

Open
lupino3 opened this issue Aug 29, 2019 · 0 comments
Open

Add a way to identify possible misconfigurations #17

lupino3 opened this issue Aug 29, 2019 · 0 comments

Comments

@lupino3
Copy link
Member

lupino3 commented Aug 29, 2019

There are some classes of errors which are not syntactic or semantic errors, but might indicate misconfiguration, and that could be considered warnings.

For example, the presence of stages that are not referenced by any feature could be considered worthy of a warning.

@lupino3 lupino3 changed the title Add a way to identify possible misconfiguration Add a way to identify possible misconfigurations Aug 29, 2019
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

No branches or pull requests

1 participant