Rework access control for `ElasticSearchViewsQuery`
Open
delta
refactoring and maintenance
- Dominant language
- Scala
- Stars
- 301
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Description
Part of the access control is done in the routes and part of it is done directly in the `ElasticSearchViewsQuery`which is confusing, those operations should all be done in `ElasticSearchViewsQuery`
Contributor guide
Research direction
Start by locating the routes and the ElasticSearchViewsQuery implementation, then trace where access control is currently applied in each. Consolidate the access-control operations in ElasticSearchViewsQuery while preserving the existing behavior; done means the routes no longer perform part of this responsibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, scala
- Domain
- authorization, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100