You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Namespaces with no operations and no sub-clients should be filtered out.
Interfaces without operations should still be included because in that case the customer is explicitly defining the interface(garbage in, garbage out),
whereas for namespaces they may be defining a models-only namespace in which case a client is unnecessary.
Check that this issue is about the Azure libraries for typespec. For feature request in the typespec language or core libraries file it in the TypeSpec repo
Clear and concise description of the problem
Namespaces with no operations and no sub-clients should be filtered out.
Interfaces without operations should still be included because in that case the customer is explicitly defining the interface(garbage in, garbage out),
whereas for namespaces they may be defining a models-only namespace in which case a client is unnecessary.
Checklist
The text was updated successfully, but these errors were encountered: