crate::Error for services #497
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
add fn Spec.operations
add TypeName
|
I'll have another PR ready with changes from ctaggart#4 to fix more data plane crates after this gets merged. |
bmc-msft
approved these changes
Nov 8, 2021
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.
Fixes #393. This adds a crate::Error to each generated services crate. It is a reexported operations::Error.
I made a bit of progress on separating out openapi and codegen in AutoRust:
TypeNameThe generated operations now quality
models::to avoid conflicts with the newErrortype. The azure-rest-api-specs are updated to commit fdf486a42c7d86dd00802414a5811d5b63c5e917.