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.

Sign up for GitHub

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

Jump to bottom

Fetch a specific namespace #187

Closed
austinkelleher opened this issue Feb 8, 2018 · 1 comment
Closed

Fetch a specific namespace #187

austinkelleher opened this issue Feb 8, 2018 · 1 comment

Comments

@austinkelleher
Copy link

Currently, the following yields every namespace:

core.namespaces('mynamespace').get((err, data) => {
  // data contains every namespace
})

I can't seem to find the recommended method of searching for a specific namespace using the following API endpoint: /api/v1/namespaces/mynamespace

Thoughts @silasbw? Thanks in advance.
silasbw pushed a commit that referenced this issue Feb 11, 2018
fix(namespaces): api.namespaces('foo') usage
cfc7fbb 
Fixes #187

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 issue Feb 11, 2018
fix(namespaces): api.namespaces('foo') usage
7031fe1 
Fixes #187

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 issue Feb 11, 2018
fix(namespaces): api.namespaces('foo') usage
7de6d75 
Fixes #187

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 mentioned this issue Feb 11, 2018
Merged
silasbw pushed a commit that referenced this issue Feb 11, 2018
fix(namespaces): api.namespaces('foo') usage
1a6e87b 
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
Copy link
Contributor

silasbw commented Feb 11, 2018

Yikes! Thanks @austinkelleher. I implemented it in #190. It will probably get merged and included with a major release in the next couple of days.

silasbw pushed a commit that referenced this issue Feb 11, 2018
fix(namespaces): api.namespaces('foo') usage
33f9e95 
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 added a commit that referenced this issue Feb 11, 2018
@silasbw
fix(namespaces): api.namespaces('foo') usage (#190)
816b957 
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@silasbw @austinkelleher