-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement JSON serialization for models #3330
Labels
Comments
timotheeguerin
changed the title
[http-client-csharp] Implement JSON serialization for models
Implement JSON serialization for models
May 13, 2024
This was
linked to
pull requests
Jun 19, 2024
This was
unlinked from
pull requests
Jun 24, 2024
This was referenced Jun 24, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 25, 2024
This PR removes the singleton pattern from all type providers to allow users to optionally override their implementation from their library. Supports #3330
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 26, 2024
This PR decouples the snippet related changes from #3603 that were added to support model serialization generation. It extends the implementation of `OptionalProvider` by overriding the base library and replacing it's instance type with the `SystemOptionalProvider` which generates an additional method in the SCM plugin. Supports #3330
This was referenced Jun 27, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Jul 1, 2024
This PR adds support for generating the `GetFormatFromOptions` method override for models that are structs. Supports #3330.
github-merge-queue bot
pushed a commit
that referenced
this issue
Jul 3, 2024
This PR adds support for generating the JsonModel Create serialization method. Supports #3330.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This task is a follow up to
Azure/autorest.csharp#4476 and covers implementing the method bodies for json serialization methods.
The text was updated successfully, but these errors were encountered: