Evolve new RPC message type and handling
Open
rpc
server
- Dominant language
- TypeScript
- Stars
- 59
- Forks
- 47
- Avg merge
- 13h 3m
- Merged PRs (30d)
- 110
Description
```[tasklist]
### Tasks
- [ ] RPC Param to take object rather than map and simplify code for deserialising to write praram names and type before calling relevant rpc handler
- [Done ] Review how the RPC registration & routing happens
```
Contributor guide
Research direction
Review how RPC registration and routing currently happen, then trace the existing RPC parameter deserialization and handler call path. The issue is done when RPC parameters are accepted as an object and parameter names and types are written before the relevant handler is called.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend-api-design
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100