oasisprotocol / oasisprotocol/explorer
Use useRuntimeTxMethodParam consistently and make it typesafe
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 13
- Avg merge
- 58m
- Merged PRs (30d)
- 2
Description
- e.g. RoflAppDetailsPage reimplements useRuntimeTxMethodParam
setMethod:in many places uses string instead of KnownRuntimeTxMethod + 'any'
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 locating RoflAppDetailsPage and the existing useRuntimeTxMethodParam hook, then search for setMethod usages that accept a string and any. Compare each implementation with the shared hook and KnownRuntimeTxMethod type. Done means the duplicated logic is consistently replaced and method values are type-safe across the affected locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100