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.
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.
@ArcturusZhang @weidongxu-microsoft , do you know if dotnet and java need the review on corresponding readme?
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.
Java does not review readme.java.md
Java automation basically override all options there.
If SDK dev need to add option, we will review it.
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.
DotNet does not need to review readme file. All dotnet related information is in the autorest.md in azure-sdk-for-net repo
I do not know Java.
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.
@weidongxu-microsoft if this is the case do we really need a readme.java.md file at all?
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.
@weshaggard
Java still have a few things to configure, e.g. https://github.com/Azure/azure-rest-api-specs/blob/main/specification/managednetworkfabric/resource-manager/readme.java.md
or #24781
Maybe the file will include a few more directives, if swagger having problem (model with duplicate name, breaking changes that can be mitigated, etc.). So it may get longer than the sample above.
I am fine about either having readme.java.md, or get rid of it and put these java configure to readme.md. At present, we generally follow the convention of putting java specific configure in readme.java.md
What I mean is that 99% of the case, the meaningful change to readme.java.md is done by SDK dev.
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.
OK I think what Ray is trying to do here is more around how to get the SDK generation owners reviewing the PRs for any SDK related impact not just the readme configuration necessarily. The readme is just an easy way to help identify PRs and assign reviewers, but it isn't a full solution to reviewing the spec PRs from and SDK generation perspective.