Possible rename of SecurityService
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
Initially `SecurityService` was envisioned as a service that would provide only security related functionality. But it is possible to execute more general functionality (for e.g. more fine grained metrics tracking, special response headers, capacity management etc) as a part of the implementation of `SecurityService`. It would be good to consider a more appropriate name for `SecurityService`.
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 reviewing the SecurityService entry point and identifying the functionality it currently represents beyond security. Check its references before deciding whether a rename is appropriate. Done means the naming question has a documented resolution and any resulting scope is clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100