Is this Bittrex client available somewhere to play with?
Regards!
Esteban A. Maringolo
2017-12-13 3:59 GMT-03:00 Ben Coman :
>
> With...
> Object subclass: #BittrexResponse
> instanceVariableNames: 'success message result'
> classVariableNames: ''
> package: 'Bittrex'
>
> Object subclass: #
> Am 13.12.2017 um 11:04 schrieb Sven Van Caekenberghe :
>
>
>
>>> On 13 Dec 2017, at 10:54, Norbert Hartl wrote:
>>>
>>>
>>> Am 13.12.2017 um 10:18 schrieb Sven Van Caekenberghe :
>>>
>>>
>>>
On 13 Dec 2017, at 10:14, Norbert Hartl wrote:
To make your core a little bit
> On 13 Dec 2017, at 10:54, Norbert Hartl wrote:
>
>>
>> Am 13.12.2017 um 10:18 schrieb Sven Van Caekenberghe :
>>
>>
>>
>>> On 13 Dec 2017, at 10:14, Norbert Hartl wrote:
>>>
>>> To make your core a little bit more reliable you should not catch the
>>> general error but a NeoJSONParseEr
> Am 13.12.2017 um 10:18 schrieb Sven Van Caekenberghe :
>
>
>
>> On 13 Dec 2017, at 10:14, Norbert Hartl wrote:
>>
>> To make your core a little bit more reliable you should not catch the
>> general error but a NeoJSONParseError. And you need to guard the dictionary
>> access. There is no
> On 13 Dec 2017, at 10:14, Norbert Hartl wrote:
>
> To make your core a little bit more reliable you should not catch the general
> error but a NeoJSONParseError. And you need to guard the dictionary access.
> There is no guarantee you get something back that inlcudes key success and
> mess
To make your core a little bit more reliable you should not catch the general
error but a NeoJSONParseError. And you need to guard the dictionary access.
There is no guarantee you get something back that inlcudes key success and
message.
Norbert
> Am 13.12.2017 um 09:54 schrieb Ben Coman :
>
hi Sven,
> On 13 Dec 2017, at 07:59, Ben Coman wrote:
> >
> >
> > With...
> > Object subclass: #BittrexResponse
> > instanceVariableNames: 'success message result'
> > classVariableNames: ''
> > package: 'Bittrex'
> >
> > Object subclass: #BittrexMarketSummary
> > inst
BTW, this is no about Zinc, but about NeoJSON.
This is what I meant with variability that is hard to capture with a simple
static type schema.
I have no time to try myself right now, but a custom mapping for ivar result
(as in a block) might be able to see the difference and act accordingly.
>
