-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add ServiceProvider Interface to azure-json and azure-xml #30635
Add ServiceProvider Interface to azure-json and azure-xml #30635
Conversation
API change check APIView has identified API level changes in this PR and created following API reviews. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
/** | ||
* Contains configuration options for creating a {@link JsonReader} or {@link JsonWriter}. | ||
*/ | ||
public final class JsonOptions { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
future concern: we probably should allow implementations to have implementation-specific options and then would need to plumb jsonoptions through clients.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep! Once we want to allow for implementation specific options we can make this class non-final
Add ServiceProvider Interface to azure-json and azure-xml
Add ServiceProvider Interface to azure-json and azure-xml
Description
Adds a
ServiceProvider
interface to bothazure-json
andazure-xml
and adds implementation of theazure-json
interface toazure-json-gson
to enable loading implementations found on the classpath. Both the JSON and XML providers also offer a default fallback when an instance cannot be found on the classpath and this is the default handling.All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines