pytest-dev / pytest-dev/pytest
introduce scopes identified by types
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
currently we have scopes as opaque strings, that somewhat relate to python things,
but clearly dont match the types of collection nodes we have
we should introduce a more nuanced mechanism so that we can better handle non-python nodes for
both code checkers and different language plugins (bdd style languages and spec type tests in yaml files come to mind)
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
The issue does not name files or tests. Start by tracing how opaque string scopes are represented alongside collection-node types, then examine the interfaces used by code checkers and language plugins. Done means a defined scope mechanism can distinguish non-Python nodes and support the mentioned plugin use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100