Lint for custom meta fields introduced into modules
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Description of feature
The guidelines say that to keep modules generally applicable, no custom meta fields should be used, but passed as parameters.
A few have managed to sneak in.
It would be nice to have a lint check that doesn't allow anything other than:
meta.method(), e.g.meta.subMap()meta.idmeta.single_endmeta.strandedness
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 existing lint checks in the Python tools package and identify where module metadata fields are parsed or validated. Confirm how the checker distinguishes the listed allowed accesses from other custom meta fields, then add coverage showing that only those forms pass and other custom fields fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100