Fix severity type for YAML converter spec #366
Merged
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
veelenga
approved these changes
Apr 5, 2023
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.
The return type of
SeverityYamlConverter.from_yamlisSeverity?, but the implementation ofYAML::Serializablepreviously swallowedNilvalues. This was recently fixed in crystal-lang/crystal#13238, so now the compiler complains about assigning a value of typeSeverity?to an ivar typedSeverity(https://github.com/crystal-ameba/ameba/actions/runs/4592466318/jobs/8109527429#step:5:24).This is only a minimal fix to make the spec succeed.
But it might be a good idea to change something about that
Niltype. I don't think it really even works to have aNilseverity.