Code changes around resource folder #1404
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olydis
reviewed
Jul 10, 2017
|
@olydis Comments addressed |
olydis
approved these changes
Jul 10, 2017
|
No modification for AutorestCI/azure-sdk-for-python |
|
No modification for AutorestCI/azure-sdk-for-node |
|
No modification for AutorestCI/azure-sdk-for-ruby |
mccleanp
pushed a commit
that referenced
this pull request
Mar 23, 2022
* Fixed the folder structure for privatepreview version swgger * Updated the readme according to the new folder structure Co-authored-by: Brijesh Khandelwal <khandelwalbrijeshiitr@gmail.com> Co-authored-by: Akash Keshari <akkeshar@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is to modify the readme file of the resources folder. Earlier (legacy branch) arm-resources is a special case folder where swagger files for features, locks,policy, resources, subscriptions and resources were included (Why? No idea!!!!!) But the files were accessed seperately. None of them is a composite file.
So, In the latest model, each of them could have a seperate folder or (as discussed with @fearthecowboy ) they could have seperate tag in the readme file. I have chosen the latter approach.
Please review and approve.