-
Notifications
You must be signed in to change notification settings - Fork 77
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
model namespaces hierarchies #2969
model namespaces hierarchies #2969
Conversation
...rkAnalytics.Management/generated/typespec-ts/sdk/test/arm-test/src/api/dataProducts/index.ts
Outdated
Show resolved
Hide resolved
packages/typespec-test/test/hierarchy_generic/generated/typespec-ts/src/classic/b/index.ts
Show resolved
Hide resolved
…spaces-as-hierarchies' into respect-model-namespaces-as-hierarchies
need to revisit the subpath user experience for ARM, data-plane, non branded. |
we can provide an option to decide if we want to export multi-level models subpath, for azure scope, it should default to false, for unbranded scope it should default to true. |
...c-test/test/NetworkAnalytics.Management/generated/typespec-ts/sdk/test/arm-test/package.json
Outdated
Show resolved
Hide resolved
packages/typespec-test/test/ai/generated/typespec-ts/src/models/index.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As offline discussed, we could restrict sub-path models
to follow the namespace convention then we could have consistant behavior with api layer.
fixes #2757