BL3P: added buy/sell/cancel

[johnnyasantoss]

Also, adds some new shiny console options for those three options.

Help for the "buy" command

ExchangeSharpConsole 0.6.2
Copyright (C) 2019 ExchangeSharpConsole

  --debug            Waits for a debugger to be attached.

  -e, --exchanges    Required. Regex of exchanges to test, null/empty for all.

  --dry-run          (Default: false) Prevents any requests from being
                     performed.

  -k, --key          (Default: keys.bin) Path to key file (generated with the
                     key utility).

  -i, --interval     (Default: 5000) Interval to fetch data in milliseconds.

  -w, --wait         (Default: false) Waits interactively.

  -r, --price        Required. The price to buy or sell at.

  -a, --amount       Required. Amount to buy or sell.

  --stop-price       The price to trigger a stop.
                     This has to be implemented and supported by the chosen
                     exchange.

  --order-type       Required. (Default: Limit) The type of order.
                     Possible values: 'limit', 'market' and 'stop'

  --margin           (Default: false) Whether the order is a margin order. Not
                     all exchanges support margin orders, so this parameter may
                     be ignored.
                     You should verify that your exchange supports margin orders
                     before passing this field as true and expecting it to be a
                     margin order.
                     The best way to determine this in code is to call one of
                     the margin account balance methods and see if it fails.

  --round            (Default: true) Whether the amount should be rounded.
                     Set to false if you know the exact amount, otherwise leave
                     as true so that the exchange does not reject the order due
                     to too many decimal places.

  -s, --symbol       Required. Symbol (currency pair) to be fetched from the
                     exchange.

  --help             Display this help screen.

  --version          Display version information.

[johnnyasantoss]

To use System.Range we would have to drop net472 as a a target framework

[jjxtra]

That's not an option unfortunately right now

[johnnyasantoss]

We already support netstandard2.0 which is compatible ¹ ² with net461. We are not using any APIs that are net472 specific (AFAIK) 🤔

[vslee]

Wouldn't that mean that we would have to drop support for netstandard 2.0 as well in order to use System.Range?

[johnnyasantoss]

That is true. One thing that I said that was wrong is that we need to drop net472 when actually what I should have said is that there's no need to support net472 when we already support netstandard20. With that clarified, I noticed that those types (Range and Index) are not available in all runtimes (only netstandard2.1 and netcoreapp30) and in that case we could use a package that ports those specific APIs to netstandard20 like this one https://github.com/bgrainger/IndexRange

[johnnyasantoss]

Maybe we could create an issue out of this conversation 🤔

[vslee]

we could use a package that ports those specific APIs to netstandard20 like this one https://github.com/bgrainger/IndexRange

Yes that's a good way to keep netstandard20 and start using the new APIs

Maybe we could create an issue out of this conversation 🤔

Yes feel free

[jjxtra]

Should be internal

[johnnyasantoss]

This can't be made internal, because, it's one of the settings of ExchangeBL3PAPI. See prop ExchangeBL3PAPI.DefaultFeeCurrency.

[jjxtra]

Looks like merge conflict, other than that I'm good to merge in

[johnnyasantoss]

@jjxtra @vslee Could you check the PR again? :)
Thanks!