interfacerproject / interfacerproject/zenflows
Better handle metadata update
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 18
- Forks
- 4
- Avg merge
- 7m
- Merged PRs (30d)
- 2
Description
Any registered user can change the metadata of an economic resource. This was necessary to update the metadata of the resource, either at the claim or starring stage. However it can obviously to security problems. It would be appropriate to handle this at the backend: specifying the operations that can be done on the metadata (e.g., add a star or remove a star, i.e., the id of the user who is starring) and not have the frontend handle the logic.
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
No files, tests, or entry points are named. Start by tracing the backend metadata update path and the frontend logic that currently permits changes; define the supported metadata operations and their authorization rules before implementing them. Done means unauthorized metadata changes are rejected and supported actions such as starring and unstarring still work through the backend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- authorization, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100