Namespace refactoring Implementation

[lmazuel]

[heaths]

I'd expect we treat the "root" namespace - if such a thing can be identified (I know it's typical, but not required, that namespaces are hierarchical) - as the crate root and any sub-namespaces as written but cased idiomatically. Under that I'd still follow guidelines that we capture clients, client options, and request models in the root and response models under a models module e.g.,

• azure_ai_language_analyze_text
  • authoring
    • models
  • models

[JeffreyRichter]

@lmazuel : This old issue is not relevant anymore, right? I say this because we agreed to Azure TypeSpec files having only 1 namespace called "Azure". Are we sticking to this or did something happen causing us to revisit the 1 "Azure" namespace.

[RickWinter]

@lmazuel : This old issue is not relevant anymore, right? I say this because we agreed to Azure TypeSpec files having only 1 namespace called "Azure". Are we sticking to this or did something happen causing us to revisit the 1 "Azure" namespace.

@lmazuel can you comment on this question