Use optionalField for creation in ExplainSMPolicy serialization #1507
+7
−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.
Description
Fixed incorrect serialization of the
creation
field inExplainSMPolicy.toXContent()
. The method was using.field()
instead of.optionalField()
for the nullablecreation
field, which is inconsistent with how thedeletion
field is handled and with the reference implementation inSMMetadata.toXContent()
.Changed line 39 in
ExplainSMPolicy.kt
:.field(SMMetadata.CREATION_FIELD, it.creation)
.optionalField(SMMetadata.CREATION_FIELD, it.creation)
This ensures proper handling of null creation workflow metadata in Explain API responses and aligns with the serialization behavior in
SMMetadata
.Related Issues
Resolves #1506
Check List
--signoff
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.