Add regression tests for extensible string enum collection serialization #9479
+62
−0
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.
Issue reported that extensible string enums in collections generated incorrect serialization code (
ToSerialString()/ToEnumName()extension methods) instead of the correct pattern (ToString()/ constructor).Investigation Result: The bug does not reproduce in the current codebase. The serialization logic correctly handles extensible enums:
MrwSerializationTypeDefinition.SerializeJsonValueCore()usesToString()for string-based extensible enumsCSharpTypeSnippets.ToEnum()uses constructor for extensible enums (structs)Changes
CreateModelWithExtensibleStringEnumCollection()helper to create test fixturesTestArrayOfExtensibleStringEnum_UsesCorrectSerialization- validatesitem.ToString()patternTestArrayOfExtensibleStringEnum_UsesCorrectDeserialization- validatesnew EnumType(...)patternExpected generated code (which is what the current implementation produces):
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.