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

cim_operations EnumerateInstances #329

Closed
KSchopmeyer opened this issue May 29, 2016 · 3 comments
Closed

cim_operations EnumerateInstances #329

KSchopmeyer opened this issue May 29, 2016 · 3 comments

Comments

@KSchopmeyer
Copy link
Collaborator

Code optionally gets namespace from ClassName parameter but documentation is unclear about this.

      ClassName (:term:`string` or :class:`~pywbem.CIMClassName`):
        Name of the class to be enumerated, in any lexical case.
        If specified as a :class:`~pywbem.CIMClassName` object, its host
        component will be ignored.
@andy-maier
Copy link
Contributor

This issue actually applies to all four EnumInstance operations (ein, ei, oein, oei).

Because the description of the namespace argument already describes the full story for namespace defaulting, I suggest that the ClassName argument just clarifies that its namespace component does play a role for namespace defaulting, and otherwise refers to the namespace argument.

Proposal:

Change the text:

If specified as a :class:`~pywbem.CIMClassName` object, its host
component will be ignored.

To:

If specified as a :class:`~pywbem.CIMClassName` object, its namespace
component will be used as a default namespace as described for the
namespace argument, and its host component will be ignored.

@andy-maier
Copy link
Contributor

This proposal should be picked up by PR #320 as far as the pull operations go, but it should also be applied to EnumerateInstances() and EnumerateInstanceNames().

@andy-maier
Copy link
Contributor

PR #320 does address this.

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

2 participants