[Update] Change JsonConverter to allow dynamic type serialization #772
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 Title:
Allow
json.JsonConverter
to support dynamic type serialization for more flexibilityPR Description:
Background / Problem:
When using
swagger-dart-code-generator
, the current implementation ofjson.JsonConverter
forces type serialization toString
, which limits flexibility when serializing custom types. For example, when attempting to serialize aDateTime
object to a Unix timestamp (int
), the code forces the output type to beString
, leading to serialization errors.Proposed Solution:
This PR modifies the generated code to use
json.JsonConverter<T, dynamic>
instead ofjson.JsonConverter<T, String>
. This change allows for more flexibility in serializing various types, such as serializingDateTime
toint
(Unix timestamp) and other custom types.Key Changes:
json.JsonConverter
to supportdynamic
types instead of forcing the output toString
.DateTime
to a Unix timestamp (int
).Test Cases:
DateTime
toint
).Related Issue:
This PR addresses issue #771.