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

Add NamespaceList v1 core enumeration #169

Closed
wants to merge 1 commit into from

Conversation

christianjoun
Copy link

This was achieved by adding the string 'namespaces' to groupResources in core.js. Thus Accessing NamespaceList v1 core api
can be easily done using
core.namespaces.get(print);.
To maintain previous functionality I renamed the default namespace (directly on the API) to namespace
(single instead of plural) and updated the alias ns. Thus accessing deployments on a given NAMESPACE can be done using
ext.namespace(NAMESPACE).deployments('').get(print);

This was achieved by adding the string 'namespaces' to groupResources in core.js. Thus Accessing NamespaceList v1 core api
can be easily done using
`core.namespaces.get(print);`.
To maintain previous functionality I renamed the default namespace (directly on the API) to `namespace`
(single instead of plural) and updated the alias ns.  Thus accessing deployments on a given NAMESPACE can be done using
`ext.namespace(NAMESPACE).deployments('').get(print);`
@silasbw
Copy link
Contributor

silasbw commented Feb 8, 2018

@christianjoun, thanks for this and sorry it slipped through the review cracks :/.

This would break existing users. Also, "core.namespace.get(print)" should already work (and if it doesn't that's a bug). Can you verify if core.namespace.get(print) has the expected result or not?

silasbw pushed a commit that referenced this pull request Feb 11, 2018
Fixes #187
Closes #169

BREAKING CHANGE: Removes default namespace feature. With a default namespace,
`api.namespaces.get` is potentially ambiguous: get the default namespaces or
get all namespaces. Remove the default namespace to be consistent with other
code.
silasbw pushed a commit that referenced this pull request Feb 11, 2018
Fixes #187
Closes #169

BREAKING CHANGE: Removes default namespace feature. With a default namespace,
`api.namespaces.get` is potentially ambiguous: get the default namespaces or
get all namespaces. Remove the default namespace to be consistent with other
code.
@silasbw silasbw closed this in 816b957 Feb 11, 2018
@Ewocker
Copy link

Ewocker commented Feb 14, 2018

Yes, it does work in 4.0.0 now. @christianjoun works with me on that. Thanks for the reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants