fix(graphql): block editor field for urlcontentmap is a json string instead of an object #31921 #32272
+157
−1
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.
Proposed Changes
_raw
are parsed as JSON and injected as objects under their corresponding base key (e.g.,blockEditor
) — only when that base key already exists.enrichWithParsedRawFields
.ContentMapDataFetcherTest
) that covers:blockEditor
whenblockEditor_raw
is present.customField_raw
do not injectcustomField
if the base key was not defined.Checklist
Additional Info
Fixes the issue where GraphQL was returning
blockEditor
as a raw JSON string instead of an object, while the REST API returned it correctly as an object.This change brings consistency between REST and GraphQL responses for
_map
fields that rely on JSON string values (specifically block editor fields). It adheres to the original field contract by only enriching existing base keys, avoiding the introduction of unexpected fields in the response.Original
Updatetd