static classes for vim.* and vmodl.* (or use static proxies and python-skeletons)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 763
- PR merge metrics
- No merged PRs in 30d
Description
For better support of IDE and other static code analysis tools it would best to have static classes with decorators to reference. This makes documentation, testing, and other tasks much easier as well. It should be possible to modify the dynamic class generators to decorate a set of static classes to match the vSphere API.
This is a big task and should not be attempted until higher priority and more critical issues are tackled.
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 dynamic class generators responsible for the vim.* and vmodl.* APIs. Define the scope for matching them with static classes or static proxies and Python skeletons, then verify that IDE support, documentation, and testing can use the resulting API representations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100