Move niscope "fancy" function metadata to addon
Open
Nobody has claimed this yet.
niscope
- Dominant language
- Python
- Stars
- 128
- Forks
- 110
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 10
Description
Description of issue
Metadata describing "fancy" functions should not be part of the main API metadata and instead should be in the Python specific addon metadata
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
Locate the niscope API metadata and the Python-specific addon metadata, then compare where the metadata for "fancy" functions is currently defined. Move that metadata out of the main API metadata and into the addon metadata, and verify that the resulting metadata remains complete and correctly separated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100