Skip to content
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

Should getVersion(program, namespace) return a VersionMap when called using child namespaces of the versioned namespace? #6281

Open
markcowl opened this issue Mar 5, 2025 · 0 comments

Comments

@markcowl
Copy link
Contributor

markcowl commented Mar 5, 2025

If a specification is created like this:

@versioned(Parent.Versions)
namespace Parent {
 @service(#{//service metadata...})
 namespace Child {
 // ... operations
 }
  namespace Sibling {
  //non-operation type definitions or operation templates
  }
}

Calling getVersion on namespace Parent.Child or Parent.Sibling it seems that the set of versions specified in the parent namespace should be returned.

Since it is a common pattern for http emitters to look for versioning on the namespace with the @service decorator, this could cause some issues for specs constructed in this way.

@markcowl markcowl changed the title Versioning: should getVersions return the set of versions in child namespaces of the versioned namespace? Versioning: should getVersion return the set of versions in child namespaces of the versioned namespace? Mar 5, 2025
@markcowl markcowl changed the title Versioning: should getVersion return the set of versions in child namespaces of the versioned namespace? Versioning: should getVersion return a VersionMap representing the set of versions in child namespaces of the versioned namespace? Mar 5, 2025
@markcowl markcowl changed the title Versioning: should getVersion return a VersionMap representing the set of versions in child namespaces of the versioned namespace? Should getVersion(program, namespace) return a VersionMap when called using child namespaces of the versioned namespace? Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant