eosjs2
eosjs2 copied to clipboard
EOSIO
Library to talk to the eos api
- [Sample code typo](https://github.com/EOSIO/eosjs2/pull/70#discussion_r221984232) - [Wrap broadcast:true in backticks](https://github.com/EOSIO/eosjs2/pull/70#discussion_r221984431)
Looks like I don't have the parameters to filter my secondary index using RPC Api: ``` /** Raw call to `/v1/chain/get_table_rows` */ public async get_table_rows({ json = true, code, scope,...
"Default" suggests to me that it should be my first choice. Really though, we don't want developers to use the default signature provider, we want them to choose one provided...
The `serializeTransaction converts tx to binary` test in `src/eosjs2-api.test.ts` passes structured data in where `serializeTransaction` expects a hex string. This failed when I strengthened error detection in 1dc9fb2b172ba5ae787dea779f018c47a1747d7a .
This depends on https://github.com/EOSIO/eos/pull/5375 (in progress).
Comparison table/matrix showing differences between eosjs and eosjs2 - [x] Basic explanation of approach and overarching themes/ideas - @chris-allnutt - [ ] Comparison Matrix/Table @randytorres
Add a mechanism for indicating a preference for which keys to use for signing a transaction.
Add a workflow/scripted process for converting the existing typedoc into gitbook.
Create or modify a tutorial app to show a more thorough use of eosjs2.