microsoft / microsoft/AzureTRE
Review how API routes are divided into separate files and change security dependencies to be per route
Open
Nobody has claimed this yet.
Copilot Agent Candidate
design
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
At present some API routes are grouped/defined in separate files, others collaged together. This should be reviewed to be consistent and manageable.
Some security dependencies are defined at the "group" of routes level, should each route have its security dependencies explicitly on the route.
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 specific files, tests, or entry points. Locate the API route definitions and review how routes are split and where security dependencies are applied. Done means route organization is consistent and each route declares its security dependencies explicitly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100