Clean up how we store model/config and how we generate model/config for python/, js/, etc.
Open
enhancement
- Dominant language
- Rust
- Stars
- 18.6k
- Forks
- 1.2k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 20
Description
We currently have a copy of model + config in the python and js directories (some of which in different formats), but, ideally, we would have one directory with the raw model/config information, and then an automated process to "port" these model/config to the various python/, js/ directories, in their own format.
Contributor guide
Assessment
This issue has not been assessed yet.