As documented, events/T permissions don't support filters
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 616
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Is your feature request related to a problem? Please describe.
This is bad. Whenever a user is allowed events/T, he can see all Ts, in contrast to e.g objects/query/T.
And this not a security hole only because it's clearly documented.
Describe the solution you'd like
Simply support filters for events/T permissions.
Shouldn't be that hard, given /v1/events already supports user-supplied filters.
Describe alternatives you've considered
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 with the documented permissions behavior and the /v1/events entry point, then trace how events/T permissions are evaluated compared with objects/query/T. Define how user-supplied filters should constrain events/T, and consider existing API behavior when determining completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100