-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[shelly] Add test coverage for thing type mapping #17040
Conversation
Signed-off-by: Jacob Laursen <[email protected]>
cool, thanks for the effort. I didn't checked that all types are in, but what I understand is that valid combinations are verified as well as invalid combos? LGTM |
I'm not sure what you mean by invalid combos, but I don't think so. The tests verify that the |
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Needed this to cherry pick into 4.2. due to another depending PR that was build on top of this. |
Signed-off-by: Jacob Laursen <[email protected]> Signed-off-by: Patrik Gfeller <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]>
Signed-off-by: Jacob Laursen <[email protected]> Signed-off-by: Ciprian Pascu <[email protected]>
This introduces some initial test coverage related to thing type and API mapping:
The intention is to document the current logic and to reduce risk when refactoring this logic.
Related to #17011