Skip to content
This repository was archived by the owner on Jul 14, 2023. It is now read-only.

Update README.md #734

Open
qiaozha wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Update README.md #734

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
309d48e
Update README.md
qiaozha Feb 7, 2021
38810a2
Merge branch 'master' into qiaozha-patch-1-1
qiaozha Apr 14, 2021
2017ffb
Merge branch 'master' into qiaozha-patch-1-1
qiaozha Apr 14, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -401,7 +401,7 @@ see [how to set an action argument as aws shorthand syntax](https://github.com/A
## SDK Customization
We also provide some SDK layer customization options. See [how to generate with different options](https://github.com/Azure/autorest.az/blob/master/doc/how-to-generate-with-different-options.md) for more details.
### Flattened SDK and un-Flattened SDK
The previous version of Autorest.Az code generator can only support the flattened SDK(before 1.6.0 release), and after we have supported the Azure CLI main repo modules(since 1.6.0 release). We are using flattened SDK by default for generating Azure CLI extensions and using un-flattened SDK by default for generating Azure CLI main repo modules.(current 1.6.1 release)
The previous version of Autorest.Az i.e. CLI code generator can only support the flattened SDK(before 1.6.0 release), and after we have supported the Azure CLI main repo modules(since 1.6.0 release). We are using flattened SDK by default for generating Azure CLI extensions and using un-flattened SDK by default for generating Azure CLI main repo modules.(current 1.6.1 release)
Current in our private releases we have changed the default generated SDK to un-flattened way as well. which should be public release very soon.
Users can use `--sdk-no-flatten` to specific an un-flattened SDK and `--sdk-flatten` to generate a flattened SDK. If users use both `--sdk-no-flatten` and `--sdk-flatten` we will still generate the un-flattened SDK.

Expand Down