Skip to content

Correct and improve checks #90

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

Merged
merged 8 commits into from
Dec 7, 2020
Merged

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Dec 3, 2020

Some of the check configurations were incorrect.

Some of the check functions were not behaving in an ideal manner.

None of the check functions were providing helpful output when they couldn't/shouldn't be run.

This PR resolves those issues.

@per1234 per1234 requested a review from silvanocerza December 3, 2020 19:26
@per1234 per1234 force-pushed the per1234/fix-check-configurations branch from dccd752 to 2eb3e40 Compare December 4, 2020 03:44
Some of the checks were incorrectly configured.
This will make it more clear to the user which think the error message is referring to.
The check functions already return this information, but the template was omitted from the error messages. Displaying
the actual file name in the error message may help the user to understand the cause of the check failure.
Return an explanatory message when it is impossible to run a check due to the required information being unavailable.
Previously, the infrastructure was in place to display this output to the user, but there was no output to display, so
you just got a confusing "notice:" output with no notice to follow.
…/checkfunctions.go

check/checkfunctions/checkfunctions.go will contain check functions that aren't specific to a single project type. There
are a large, ever increasing, number of tests for check functions, and each group of check function types may have
different testing requirements, so it's helpful to split them up a bit.
This makes the superproject type accessible to the check functions. This allows the check to determine whether the
project is a subproject, which may require different handling.
The superproject should have a readme, but it's not necessarily essential for the subproject to have one as well.
@per1234 per1234 force-pushed the per1234/fix-check-configurations branch from 2eb3e40 to 12170ff Compare December 4, 2020 21:21
@per1234 per1234 merged commit f22ed88 into main Dec 7, 2020
@per1234 per1234 deleted the per1234/fix-check-configurations branch December 7, 2020 10:24
@per1234 per1234 added topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project labels Sep 29, 2021
@per1234 per1234 self-assigned this Nov 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants