QuantConnect / QuantConnect/lean-cli
--zerodha-history-subscription shouldn't always be required
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 326
- Forks
- 168
- Avg merge
- 3d 50m
- Merged PRs (30d)
- 3
Description
If we run
lean live deploy "<project>" --brokerage "Paper Trading" --data-provider-live zerodha --data-provider-historical Local
we get
Error: You are missing the following options: --zerodha-api-key, --zerodha-access-token, --zerodha-product-type, --zerodha-trading-segment,
--zerodha-history-subscription
but --zerodha-history-subscription shouldn't be required since we aren't using Zerodha for historical data.
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing the lean live deploy command with Zerodha as the live data provider and Local as the historical provider, then trace the CLI validation for the Zerodha options. Done means --zerodha-history-subscription is not required when historical data comes from Local, while the other required options remain validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100