Update decisioning-content datatype to use xdm: shorthand field names#2172
Open
kmmraju wants to merge 1 commit into
Open
Update decisioning-content datatype to use xdm: shorthand field names#2172kmmraju wants to merge 1 commit into
kmmraju wants to merge 1 commit into
Conversation
Replace full namespace URLs (https://ns.adobe.com/experience/decisioning/*) with standard xdm: shorthand aliases for contentType and content fields in schema definition and example files. This datatype is not yet deployed to stage or prod, so the field name change is safe. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Replace full namespace URLs (https://ns.adobe.com/experience/decisioning/*) with standard xdm: shorthand aliases for contentType and content fields in schema definition and example files. This data type is not yet used in stage or prod, so the change is safe.
As part of the testing, we found that using full namespace URLs adds additional roots before the actual fields. In this case, the "experience/deciding" root is prefixed to the content & contentType fields, which is undesired.