Fix OTC candle data parsing field order #50
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OTC candles from
get_candles()all appeared RED/DOJI because the parser assumed wrong field order. Server sends[timestamp, open, close, high, low], not[timestamp, open, low, high, close].Changes
_parse_candles_data: Fixed field mapping to readclosefrom index 2,highfrom 3,lowfrom 4_parse_stream_candles: Changed minimum length check from 6 to 5 elements for consistencyBefore/After
Reference format confirmed via BinaryOptionsTools-v2 candle parser.
Original prompt
This section details on the original issue you should resolve
<issue_title>All retrieved OTC candles RED issue</issue_title>
<issue_description>The candles returned from get_candles("GBPJPY_otc", 60, 20) are not real.
They don’t reflect the actual chart — all are red or doji.
Looks like something is wrong with how OTC data is fetched or interpreted.
Please check.
My code: