fix whoxy verification (type-safe) #1867
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lc
changed the title
zricethezav
added
the
Hacktoberfest-Detector-Competition-Fix
|
@lc This isn't a large enough improvement to be considered. If a change like this were to qualify it would be easy to rack up points without doing much work. |
zricethezav
added
invalid
zricethezav
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This pull-request fixes Whoxy verification and the verifier implements type safety.
Using a struct to ensure
Status== 1 is (or should be?) preferable to string manipulation.Checklist:
make test-community)?make lintthis requires golangci-lint)?