-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Test cargo lints #5614
Test cargo lints #5614
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really happy to see tests for the cargo lints 🎉
Just a minor nit - looks good to me overall!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall. Maybe we should add a test (not necessarily in this PR) that ensures, that there are no stderr
files in the pass
dirs
Fix missing `authors` entry in the provided example
Make the output of the lint deterministic by sorting the versions
@flip1995 I think the test you mention is a good idea! But I've been thinking about a limitation of this implementation, that we could need in some cases to have multiple fail/pass manifests, for example if we want to test multiple values for the same attribute. I plan to work on #5041 soon, I think it could be a good excuse to try to come up with a solution to the limitation I mentioned. Since this will probably have an impact in the filesystem layout, I think I could implement the test in that PR. What do you think? |
Instead of checking On the other hand, why would they even have to be named |
Indeed, that's much simpler, I like it 👍 I will make the changes needed and rework a bit the documentation. Thanks! |
So I've applied the discussed changes. I went for leaving the fail/pass directories by default because I think it's good to enforce having at least one of each cases and IMO it's easier to understand for most of the cases. I think the test is not viable anymore as the nomenclature is not enforced, let me know if you think otherwise. |
Having
Yes, with this, we won't need the test. |
Thanks! @bors r+ |
📌 Commit f9013ff has been approved by |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
changelog: Add infrastructure to test cargo lints
Closes #5603