WMI Adapter updates
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
Support:
- set
- export
- delete
- method invocation
Proposed technical implementation details (optional)
Many WMI classes support methods. We should maybe just have a WMIMethodInvocation metaclass that takes the namespace, class, method name, and a property bag (key/value pairs) that would be the inputs to the method. The only problem with this approach is that the user needs to know all that info.
Alternatively, but would be noisy when listing, is to have dynamic instances returned that represent each method that can be called.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the WMI adapter and determining how its supported operations are represented. Review the proposed metaclass and dynamic-instance approaches, then define how set, export, delete, and method invocation should be exposed. Done means the agreed WMI operations are implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100