Skip to content

Make ui_class optional#32

Merged
tetienne merged 1 commit intomasterfrom
fix/ui_class_is_optional
Aug 6, 2020
Merged

Make ui_class optional#32
tetienne merged 1 commit intomasterfrom
fix/ui_class_is_optional

Conversation

@tetienne
Copy link
Copy Markdown
Collaborator

@tetienne tetienne commented Aug 6, 2020

@tetienne tetienne requested a review from iMicknl August 6, 2020 07:07
Copy link
Copy Markdown
Contributor

@vlebourl vlebourl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess that's enough on the API side. For HA, we need to consider how to classify an entity that doesn't have a uiClass as we map the Somfy widgets and ui_classes to the Home Assistant platforms.

@tetienne
Copy link
Copy Markdown
Collaborator Author

tetienne commented Aug 6, 2020

@vlebourl That's an edge case, the device returned is marked as "not available". On HA side, we already handle this case. We map the None value... to nothing. We will see if "real" device will come with this behavior.

@tetienne tetienne merged commit 84cbb02 into master Aug 6, 2020
@tetienne tetienne deleted the fix/ui_class_is_optional branch August 6, 2020 07:23
tetienne added a commit that referenced this pull request Feb 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

TypeError: __init__() missing 1 required keyword-only argument: 'ui_class'

3 participants