QuantConnect / QuantConnect/Lean
Custom data can't update OHLC security properties
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 21.7k
- Forks
- 5.3k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 34
Description
Expected Behavior
Custom data types should be able to update security OHLC properties if they contain user defined OHLC fields that follow a name convention (e.g: "Open", "High", etc.)
Actual Behavior
Custom data types update all OHLC security properties with a single fixed value from their Value attribute
Potential Solution
N/A
Checklist
- I have completely filled out this template
- I have confirmed that this issue exists on the current
masterbranch - I have confirmed that this is not a duplicate issue by searching issues
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the custom data handling and the code that updates security OHLC properties, then identify the existing tests for custom data or OHLC values. Done means user-defined Open, High, Low, and Close fields update their corresponding security properties instead of applying the single Value to all of them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100