feat: update metadata block payload transformation to support deep nesting - #478
Open
vera wants to merge 2 commits into
Open
feat: update metadata block payload transformation to support deep nesting#478vera wants to merge 2 commits into
vera wants to merge 2 commits into
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:
Updates dataset metadata payload transformation to support deeply nested metadata fields. This aligns the JavaScript client with the Dataverse API, which already supports unlimited nesting.
Which issue(s) this PR closes:
None
Related Dataverse PRs:
None
Special notes for your reviewer:
None
Suggestions on how to test this:
Verify that dataset metadata blocks with multiple levels of nested fields are transformed correctly from the API payload into the dataset model. A unit test was added to cover deeply nested metadata fields.
Is there a release notes or changelog update needed for this change?:
Yes. This is a client behavior improvement that would be worth noting in the changelog. I've updated the changelog.
Additional documentation:
None