lmstudio-ai / lmstudio-ai/lmstudio-python
SDK schema export: consume config key to KV config field name mapping
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 875
- Forks
- 166
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/lmstudio-ai/lmstudio-js/issues/253 is an `lmstudio-js` feature request to also publish a data file that specifies how to map `LlmPredictionConfig`, `LlmLoadModelConfig`, and `EmbeddingLoadModelConfig` attributes to `KvConfigStack` field names.
This corresponding Python SDK issue covers updating the SDK data model generator to add that data file into the `lmstudio` package, and updating `_kv_config.py` to use it when mapping configuration keys, rather than maintaining the mappings independently of `lmstudio-js`.
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
Start by reading the SDK data model generator and _kv_config.py, then review the corresponding lmstudio-js feature request at issue 253 for the mapping data format. Done means the generated data file is included in the lmstudio package and _kv_config.py uses it instead of maintaining independent mappings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- api, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100