Open
Conversation
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
1 participant
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.
What this PR does / why we need it:
This PR relaxes the typing of the UpdateCollection use case to allow partial collection updates.
Native Dataverse collection updates do not require a fully populated object, only the fields to be changed need to be provided.
This change aligns the client typing with that behavior and avoids unnecessary TypeScript warnings in downstream usage.
This is a typing-only change with no runtime impact.
Which issue(s) this PR closes:
Related Dataverse PRs:
Special notes for your reviewer:
TypeScript typing change only (Partial)
No API or runtime behavior changes
Suggestions on how to test this:
Is there a release notes or changelog update needed for this change?:
Additional documentation: