Ultraviolet Enum Returning Incorrect Values #42
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
|
Thank you sooooo much for this! ❤️ |
null8626
added a commit
that referenced
this pull request
Jun 20, 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.
wttr.in has UV values ranging from 1 to 12. This is supposed to get mapped to LOW, MODERATE, HIGH, VERY_HIGH, or EXTREME. However, the mapping is incorrect due to declarations using the auto keyword. e.g. If wttr returns a UV value of 5, EXTREME gets returned instead of MODERATE.
By starting the enum values at 13, it is outside the range of valid wttr values, so it will return the correct enum value.