InvokeAI/invokeai/frontend
psychedelicious a3b11c04cb fix(ui): model metadata handlers use model identifiers, not configs
Model metadata includes the main model, VAE and refiner model.

These used full model configs, as returned by the server, as their metadata type.

LoRA and control adapter metadata only use the metadata identifier.

This created a difference in handling. After parsing a model/vae/refiner, we have its name and can display it. But for LoRAs and control adapters, we only have the model key and must query for the full model config to get the name.

This change makes main model/vae/refiner metadata only have the model key, like LoRAs and control adapters.

The render function is now async so fetching can occur within it. All metadata fields with models now only contain the identifier, and fetch the model name to render their values.
2024-02-26 14:49:38 -05:00
..
CLI Resolving merge conflicts for flake8 2023-08-18 15:52:04 +10:00
install remove startup dependency on legacy models.yaml file 2024-02-23 07:47:39 +11:00
merge remove startup dependency on legacy models.yaml file 2024-02-23 07:47:39 +11:00
training remove startup dependency on legacy models.yaml file 2024-02-23 07:47:39 +11:00
web fix(ui): model metadata handlers use model identifiers, not configs 2024-02-26 14:49:38 -05:00
__init__.py Run python black 2023-07-28 09:46:44 -04:00
legacy_launch_invokeai.py isort wip 2023-09-12 13:01:58 -04:00