oasisprotocol / oasisprotocol/oasis-core
expose a list of transaction methods
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
SUMMARY
we actually have pretty good introspection, with existing facilities to detect method name collisions and to look up the transaction body type of a given method.
for generating bindings in other languages, we'd like to have access to the list of registered methods. currently there's a private map of method names to body types, which may work for this purpose
note that even if this were exported, it would be up to the program to make sure the necessary modules are initialized in order for those modules to register their transaction names
ISSUE TYPE
- Feature Idea
COMPONENT NAME
consensus transactions
ADDITIONAL INFORMATION
for our client-sdk ts-web reflect-go project
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
Start in the consensus transactions introspection code, tracing the existing private map from method names to transaction body types. Check how the client-sdk ts-web reflect-go project would consume the registered methods; done when callers can obtain the method list after the relevant modules initialize.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100