Problem description
Currently, the model constants don’t give much intuition about what each model is for, and so users need to reference documentation to know which models are available and what they’re used for. This problem also extends to Hugging Face, where models are listed ungrouped.
Proposed solution
- Prefix names with model categories - maybe similar to how it is done in style transfer.
- On Hugging Face, create collections that group models by the hook/module they are designed for.
Then in the hook docs, we could replace links to specific models with links to the related collection, so users can easily browse all supported models for that hook.
Alternative solutions
Add JSDoc to model constants.
Benefits to React Native ExecuTorch
Users would be able to quickly identify what a model does without looking up the docs. This would reduce confusion and improve developer experience.
Additional context
No response
Problem description
Currently, the model constants don’t give much intuition about what each model is for, and so users need to reference documentation to know which models are available and what they’re used for. This problem also extends to Hugging Face, where models are listed ungrouped.
Proposed solution
Then in the hook docs, we could replace links to specific models with links to the related collection, so users can easily browse all supported models for that hook.
Alternative solutions
Add JSDoc to model constants.
Benefits to React Native ExecuTorch
Users would be able to quickly identify what a model does without looking up the docs. This would reduce confusion and improve developer experience.
Additional context
No response