`Clients.matchAll()` should exclude the current environment
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
With #1036 and #955 we create the possibility to use Clients.matchAll() in a way that would match the currently executing environment. This would probably be surprising to callers. I think we should exclude the "self" environment automatically. If developers end up wanting it for some reason we could add a includeSelf:true option in the future.
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 reading issues #1036 and #955 to understand how Clients.matchAll() can include the current environment. Define the behavior so the current environment is excluded by default, and verify that the specification clearly states the resulting matching semantics; an includeSelf option is only a future possibility mentioned in this issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100