OpenBankProject / OpenBankProject/OBP-API
Update View sets all permissions to false, when not beeing explicitly set
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 482
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 15
Description
Endpoint-Version
2.2.0
Expected Behaviour
When updating a view with a new permission, e. g. canAddCounterparty, the other permissions won´t be affected when not explicitly set.
Actual Behaviour
Every single permission that already is true has to be set again in order to stay the same as before
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
Start by locating the view-update endpoint and its permission parsing or persistence logic, then reproduce the behavior described for endpoint version 2.2.0. Check how omitted permissions are handled during an update. Done means updating one permission preserves all previously enabled permissions that were not explicitly changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100