Don't serialize to json ETS properties for DateTime and string types #15665
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.
PR Summary
PowerShell automatically adds extended properties to
DateTime(specificallyDisplayHint) objects that is used with formatting. This is intended to be "internal", but when converted to JSON, those extra properties turn what should be a json datetime to a complex object. Forstringtypes, if the user has added extended properties, this can result in recursive serialization behavior.The @PowerShell/powershell-committee agreed to special case both
DateTimeandstringtypes to not serialize any extended properties when converting to JSON.PR Context
Fix #5797
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.(which runs in a different PS Host).