Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add API in compiler for easily calling all native contract methods #2495

Open
spencercorwin opened this issue Jun 26, 2021 · 0 comments
Open
Labels
area/compiler Categorize issue or PR as compiler (@neo-one/smart-contract-compiler) related kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed.

Comments

@spencercorwin
Copy link
Collaborator

Currently users can do this with our linked smart contract API but we could make native contract calls way more user friendly be exposing them directly with something like Native.Ledger.getBlockHash(<index>). This is just an idea. Or maybe we want to expose all those native contract methods in a module like Blockchain.getBlockHash(<index>). Either way all those native contract methods should be exposes very easily to the user in some way.

Make sure to add docs and tests.

@spencercorwin spencercorwin added kind/feature Categorizes issue or PR as related to a new feature. area/compiler Categorize issue or PR as compiler (@neo-one/smart-contract-compiler) related kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/important-longterm Important over the long term, but may not be staffed. labels Jun 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/compiler Categorize issue or PR as compiler (@neo-one/smart-contract-compiler) related kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed.
Projects
None yet
Development

No branches or pull requests

1 participant