Extra examples

[grctest]

Work in progress

Related to: bitshares/beet#207

[grctest]

Operations 32, 34, 36, 69 and 71 need a peer review, I wasn't sure what the input format was supposed to be like where marked // TODO: DEBUG

Also, should blank future extensions be included as extensions: [] or extensions: null?

[abitmore]

Thanks!

[abitmore]

Also, should blank future extensions be included as extensions: [] or extensions: null?

IIRC API nodes always accept extensions: [], and for some operations extensions: {}, but not always accept extensions: null.

[sschiessl-bcp]

With the current beet rc I get stuck doing this

>> node ./bitshares/injections/001_limit_order_create.js 
received connected socket response
socket: authenticated
Connected to Beet
sending link request
sending linkRequest request
sending api request

No popup visible. Which Beet version / commit hash are you using?

[grctest]

@sschiessl-bcp Please use the following Beet PR: bitshares/beet#222

I've introduced several fixes to address the issue you ran into, including:

• Tweaks to establishing blockchain connection when switching between blockchains BTS<->BTS_TEST
• Timeouts have been introduced to several functions
• More verbose error checks to reject erroneous injected parameters

I too wasn't getting the prompt, now I do get it in both production and testnet. If the prompt still doesn't show, try different asset ids etc?

[sschiessl-bcp]

see bitshares/beet#222