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

Issue warnings on empty folders #169

Merged
merged 1 commit into from
Jan 12, 2021
Merged

Issue warnings on empty folders #169

merged 1 commit into from
Jan 12, 2021

Conversation

paulo-ferraz-oliveira
Copy link
Collaborator

Closes #146.

Since this is a warning, not a hard error, and there's no output (except for the visible message), I couldn't think of a nice enough test. Suggestions?

Note: I add the possibility to write warnings, in magenta, since I want to distinguish these from errors.

Helps keep a trimmed down elvis.config

Example output:
Warning: Searching for files in ["test/examples/2"] yielded none. Update your configuration.
@elbrujohalcon
Copy link
Member

I don't think we have tests in place for any of these things (I mean… just with a quick grep… I couldn't find any test for error printing either). Maybe we test these things indirectly from elvis? 🤔

I'm fine if you don't want to spend more time trying too hard to test this. If you're already done with this, I'll go ahead and merge it as-is.

@paulo-ferraz-oliveira
Copy link
Collaborator Author

I'd appreciate it if you'd at least try it out and tell me if the UX is good. Other than that, I'm OK for merge.

@elbrujohalcon elbrujohalcon merged commit 19bfe9f into inaka:master Jan 12, 2021
@paulo-ferraz-oliveira paulo-ferraz-oliveira deleted the feature/warn_on_empty_folders branch January 13, 2021 01:29
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.

Warn on empty analysis
2 participants