`_scope` canonical property
Open
Nobody has claimed this yet.
Issue-Enhancement
Needs Triage
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
There may be sufficient resources that can act on the user or the system such that it makes sense to have this well-defined vs different for different resources.
_scope: [currentUser | allUsers]
Does allUsers also mean system or should that be a separate value? If not specified, expectation is default is currentUser. Are there other scopes that should be considered?
Proposed technical implementation details (optional)
No response
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 names no files, tests, or entry points. First find how canonical properties are defined and scoped, then resolve the open questions about currentUser, allUsers, system, defaults, and other values; done requires an agreed scope model with corresponding implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100