Flytte console-backend rbac -> api repo
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 2
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 17
Description
Dagens console-backend RBAC feature bør flyttes inn som en del av repoet til API.
Featuren bør også renames.
Contributor guide
No contributing guide indexed for this repository
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 mapping the current console-backend RBAC implementation and the API repository structure. Confirm which RBAC functionality must move, decide the replacement name for the feature, and document the migration boundaries. Done means the feature belongs in the API repository under its agreed new name without leaving the old implementation behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, authorization
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100