Decode memo fields in UI
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Send memo fields in event history to /decode endpoint to decode in the UI.
Describe alternatives you've considered
Additional context
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 tracing how event history is rendered in the UI and how requests to the /decode endpoint are currently made. Determine where memo fields are represented and how decoded values should appear in event history. Done means event-history memo fields are sent for decoding and displayed in decoded form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100