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

Ensure entrypoint params are always named #81

Open
purcell opened this issue Apr 13, 2021 · 1 comment
Open

Ensure entrypoint params are always named #81

purcell opened this issue Apr 13, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@purcell
Copy link
Contributor

purcell commented Apr 13, 2021

When deployed, some entrypoint parameters are numbered rather than named, which means the contract is a little less self-describing than it should be. Let's see if we can fix it, perhaps by supplying params as typed structs?

See the "Entrypoints" tab here: https://edo.tzstats.com/KT1QYTVYqpnTDR56uY42cNp4GNEGU2oMJeBr

@purcell purcell added the enhancement New feature or request label Apr 13, 2021
@purcell
Copy link
Contributor Author

purcell commented Apr 15, 2021

This one is a bit annoying, because it involves declaring the parameter types in a separate file to the endpoints; putting the types in checker.mli isn't enough because they need to be repeated in checker.ml, and if placed in checkerTypes.ml (for example) then the documentation will be fragmented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant