Improve handling of defaults and serialization/deserialization of Thing Descriptions #189
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.
This PR fixes a couple of issues I noticed when it comes to the (de)serialization behavior of Thing Descriptions. It also exposes an unnamed constructor for the
ThingDescription
class, which can have advantages in certain scenarios in comparison to the deserialization approach (from aMap<String, dynamic>
).As this PR contains some breaking changes, it will trigger the release of version 0.35.0.