You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I don't think it is possible to create such code that will so intuitive here, so user could refer to a model without even looking once into documentation. The PR #748 adds organised section of models for each task, links it clearly in documentation. This way it solves the mentioned problem in a different way. That's why I will mark it for resolving by the PR.
The is an idea to not only suggest list of models from documentation, but also from the level of language server (e.g. tabbing in VSC). The proposed solution might look like this:
Activity
docs: Update warnings and links in docs (#659)
msluszniak commentedon Feb 2, 2026
I don't think it is possible to create such code that will so intuitive here, so user could refer to a model without even looking once into documentation. The PR #748 adds organised section of models for each task, links it clearly in documentation. This way it solves the mentioned problem in a different way. That's why I will mark it for resolving by the PR.
msluszniak commentedon Feb 2, 2026
The is an idea to not only suggest list of models from documentation, but also from the level of language server (e.g. tabbing in VSC). The proposed solution might look like this:
docs: Add autogenerated API for React Native ExecuTorch documentation (…
mkopcins commentedon Mar 25, 2026
The final approach would be as follows:
With this we achieve following:
refactor: rename paraphrase-multilingual export to _QUANTIZED suffix
feat(constants)!: switch URLs to v0.9.0 layout + add MODEL_REGISTRY (#…