Issue #73: Preserve normalized output from nested Typed Relation fields inside Paragraphs #74
Conversation
This file contains 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
…d Relation fields inside paragraphs.
rosiel
reviewed
Sep 18, 2024
|
I encountered a bug in this solution. When the typed relation field is attached directly to the node (e.g. the classic Linked Agent setup) rather than in a paragraph, then the author names are pulled too many times. 
|
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.
Resolves Issue #73.
Scenario that this fix addresses:
Create a field structure like this:
Contributor Paragraph
Where Contributor Paragraph may have more than one instance.
Before the Field Item List normalizer was looping over Field Items and overwriting them , so only the last one was being printed.
Now multiple names show up as expected.
Let me know if I can provide any more info.