fix: iconImage in an app response is optional#252
Merged
rossiam merged 1 commit intoSmartThingsCommunity:mainfrom Jan 13, 2025
Merged
fix: iconImage in an app response is optional#252rossiam merged 1 commit intoSmartThingsCommunity:mainfrom
rossiam merged 1 commit intoSmartThingsCommunity:mainfrom
Conversation
🦋 Changeset detectedLatest commit: a9ec956 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Sitlintac
approved these changes
Jan 13, 2025
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
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.
Changes
iconImagefield as optional in response from APICONTRIBUTING.mddocument to make things more clearNotes
The
iconImagefield is an object which contains a singleurlkey which means there are three possible ways this can be defined:iconImagefield is omitted entirely.urlis not. ("iconImage": {})urlpopulated. ("iconImage": { "url": "<my-url>" })When submitting data to the API, all three are accepted and work as expected.
When retrieving data, option 2 is sensibly never returned, normalizing to option 1 if option 2 was submitted via creation.
So, the type used for creation and updating was left as
iconImage?: IconImagewhich allows for all three cases, but the type for the return value was changed toiconImage?: Required<IconImage>which allows for options 1 and 3. (The previous value oficonImage: Required<IconImage>allowed only for option 3.)