For now, we're basing our client objects on the ClientBase class, which uses a dictionary with the attributes "timestamp", "open", "high", "low", "close" and "volume". This is hardcoded whenever the candlestick is interfaced (at the moment this was written, only at src/app/clients/binance/binance_client.py and at src/app/services/consumer_service.py).
We should have an exclusive object to handle this data, having a consistent schema and avoiding checking if the keys are present.
For now, we're basing our client objects on the
ClientBase
class, which uses a dictionary with the attributes "timestamp", "open", "high", "low", "close" and "volume". This is hardcoded whenever the candlestick is interfaced (at the moment this was written, only atsrc/app/clients/binance/binance_client.py
and atsrc/app/services/consumer_service.py
).We should have an exclusive object to handle this data, having a consistent schema and avoiding checking if the keys are present.