this was the big problem that was a huge hiccup.
it is now solved.
The next thing is just getting the buttons to work the way they're expected to
other than that it's all fine.
the correct thing to do at this point is to factor out "show a yes/no popup
window to user"
the complexity in "open a window and then execute some code in the context of
that window" is mind-boggling
nothing works
* Adjusting version
* Initiating some edoc stuff
* Doc check
* Fixing docs
* Do a hard type check when entering nodes
* Two fixes:
- Module call change from enacl to ecu_eddsa
- Fix the v3 call endpoint for top block
* Fix top_block typespec and make top_height great again
* Fix typo
* Coerce in both directions
This is what I have been using in the voting app, via decode_bytearray.
Some smaller fixes are included too, such as exposing the `state` type
of a contract, and wrapping/unwrapping the `{tuple, {...}}` wrapper
produced by aeser.
Add Contract.state to the AACI typedefs
dry_run_result and tx_result
Coerce now has the ability to convert BACK from the format aebytecode
understands, which allows dry_run_result and tx_result to decode the
cb_... stuff and turn it into the kinds of erlang object that could be
passed right back into vanillae, for example. More than anything,
though, these functions just give you the data in the form that you want
it for pattern matching and getting actual work done.
expose decode_bytearray instead of tx_result
wrap/unwrap tuple atom correctly
* better coerce error accumulation
Now coerce errors all have the same format: [{error(), [path_steps()]}]
Blake was being stupid so I copied the contents of this package directly into
the source of JR, but really this should be its own package. So now doing that
refactoring.
pharpend
Craig Everett