QuantConnect / QuantConnect/lean-cli
Extend stored project parameters
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 326
- Forks
- 168
- Avg merge
- 3d 50m
- Merged PRs (30d)
- 3
Description
- Project parameters are currently a key, value collection. But ideally we should be able to store the min/max/step properties too, so they are stored when performing an optimization
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 tracing how project parameters are stored and how optimization parameters are passed through the CLI. Determine where key/value parameters are serialized, then identify the existing optimization flow and tests that cover parameter persistence. Done means min, max, and step properties are retained when an optimization is performed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100