Repository navigation
fix: make componentType optional in EvvaComponent - #195
Merged
Merged
Conversation
The MQTT API can return EVVA components without a componentType, which caused query responses to fail parsing. Unknown component types are now coerced to null like other optional enums. Closes: #194 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
EvvaComponent.componentTypeis now optional (ComponentType? = null), since the MQTT API can return components without it (e.g.{"id": "...", "upgradeMedia": true}).null, like other optional enums.componentType; tests that used an unknowncomponentTypeas an unparsable payload now use a missingidinstead.Note: the property type changes to nullable, so consumers accessing
componentTypedirectly need to handlenull.Closes: #194
🤖 Generated with Claude Code