-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support multiple namespaces in client library code generation #4537
Comments
To clarify, we need to support multiple namespaces also for unbranded scenario and the scope includes c#, Java, Python, JS Modular |
There is models under For now, unbranded won't do any default namespace mapping, so they would appear at Do we need to do a mapping for models from this |
python has added support for this in our latest generator, so removing the python label |
Clear and concise description of the problem
Currently, code generators for .NET, Java and Python only support generating client library in a single namespace. Generators use the namespace defined in tspconfig.yaml and ignore the namespaces defined in TypeSpec. This works when we only have a single namespace.
However, there are cases where we need multiple namespaces in the generated library to allow different clients to be in different namespaces (for e.g. OpenAI and Search). So, the proposal is for generators to use the namespaces defined in TypeSpec as the namespaces in client libraries too and not use tspconfig.yaml.
More details on the proposal can be found here.
Checklist
Spec
Implementation
The text was updated successfully, but these errors were encountered: