Should we allow a client to be deleted or edited?
Open
Nobody has claimed this yet.
question
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
There are different reasons why a user might want to to edit or delete a client e.g. if there is a new instance URL or the service has been deprecated. In these situations, how do we manage associated credentials when a client is deleted or edited?
cc: @taylordowns2000 @stuartc
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
The issue names no files, tests, or entry points. First clarify whether clients should support editing or deletion and define how associated credentials must be handled; done requires an agreed behavior and implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100