Skip to content
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

[Schema Registry] Add convenience layer for SchemaRegistryClient #13946

Closed
ramya-rao-a opened this issue Aug 4, 2020 · 0 comments · Fixed by #13657
Closed

[Schema Registry] Add convenience layer for SchemaRegistryClient #13946

ramya-rao-a opened this issue Aug 4, 2020 · 0 comments · Fixed by #13657
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved. Schema Registry

Comments

@ramya-rao-a
Copy link
Contributor

This issue is a follow up for #13471

Using the Java SchemaRegistryClient as a reference, add a convenience layer to the generated client in @azure/schema-registry package applying .Net SDK guidelines.

The corresponding package in Java has interfaces for Codec and Serializer. As part of this issue, we will be not be focusing on these and only be adding a layer over the auto generated code.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 4, 2020
@ramya-rao-a ramya-rao-a added Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved. Schema Registry labels Aug 4, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 4, 2020
@ramya-rao-a ramya-rao-a added this to the [2020] September milestone Aug 4, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Mar 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved. Schema Registry
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants