fix: iconImage in an app response is optional #252
Merged
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
iconImage
field as optional in response from APICONTRIBUTING.md
document to make things more clearNotes
The
iconImage
field is an object which contains a singleurl
key which means there are three possible ways this can be defined:iconImage
field is omitted entirely.url
is not. ("iconImage": {}
)url
populated. ("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?: IconImage
which 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.)