a few extensions about cryptocompareapi HOT 4 CLOSED

Yes I've been working on adding the optional fields and limits, and the debugging is a good idea. I'll have this updated in the next few weeks.

from cryptocompareapi.

Here's a couple more things:

It might be best for the routine to return data guaranteed to be time-sequenced. I've modified my code above to use a TreeMap and also modified the rejection of duplicate timestamps to use that instead.

Also there's the possibility of loss of precision converting stringed numbers to doubles. Might it not be better to use BigDecimals or something similar?

from cryptocompareapi.

Cryptocompare is now sending null data tuplets for dates when it has no values. I've added this code:

`// CryptoCompare is now sending empty values instead of saying it has no data, eg:
// Data [time=1434664800 (2015-06-18T22:00:00Z), open=0.0, high=0.0, low=0.0, close=0.0, volumeFrom=0.0, volumeTo=0.0]
// Iterate through the time-sorted list deleting everything until we find the first real data.

	Iterator<Integer> iter = mapData.keySet().iterator();
	
	while (iter.hasNext()) {
		Integer k = iter.next();
		
		Data v = mapData.get(k);
		
		if (v.open == 0.0d
				&& v.high == 0.0d
				&& v.low == 0.0d
				&& v.close == 0.0d
				&& v.volumeFrom == 0.0d
				&& v.volumeTo == 0.0d) {
			iter.remove();
		} else {
			break; // stop when we reach first real value
		}

	}`

from cryptocompareapi.

After working on different projects for some time, I came back and implemented these features.

from cryptocompareapi.