Refactor all the types in azure_core to match typespec_client_core #2181
Labels
Azure.Core
The azure_core crate
Client
This issue points to a problem in the data-plane of the library.
Milestone
When refactoring most of the general types into
typespec
andtypespec_client_core
, I did my best to keepazure_core
looking like it did to avoid an even bigger diff with all the changes to imports in other crates. All those other crates also helped double check my progress. Moving those types around became a lower priority.After beta.1, I'd like to move those types around to match
typespec_client_core
. I'm pretty happy with the layout - though, open to suggestions otherwise - and I think re-exporting fromazure_core
that the emitter uses makes sense. Azure service partners will interface entirely withazure_core
- which does and will continue to have some Azure-specific types like pagers and pollers - and it gives us flexibility as well.This will no doubt require changes in the emitter, but my hope is that few to no type names will need to change - just their module paths.
The text was updated successfully, but these errors were encountered: