Use `frame-decode` for decoding storage keys in subxt?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 293
- Avg merge
- 18h 35m
- Merged PRs (30d)
- 3
Description
Perhaps we can simplify Subxt and remove the storage key decoding logic by relying on frame-decode instead?
(side effect: this might also lead to useful frame-decode feedback as well as meaning we only decode things in one place)
If doing this makes everything more complicarted in subxt or proves to not be worth while then no worries, but probably worth a shot!
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
The issue names no files or tests. Start by locating Subxt’s storage-key decoding logic and the corresponding frame-decode functionality, then compare their responsibilities and complexity. Done means determining whether delegating decoding to frame-decode simplifies Subxt without making it more complicated, with any useful frame-decode feedback identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100