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
Using CatalogFiltered and addonCatalogs for addons is great, but it has a flaw: there are no installed addons in the catalog
this can be solved:
at a UI level, add another route /installed which just displays ctx.content.addons with some filtering
by wrapping CatalogFiltered and adding installed by splitting the Load action into Installed(type) or Catalog(resource_ref); this has two extra advantages:
allows to structure the navigation conveniently at a model level (we can choose between catalog -> type or type -> catalog)
different Load action for addons; otherwise we have to wire msgs in the app in such a way that only model.discover or only model.addons will receive a certain Load
Using
CatalogFiltered
andaddonCatalogs
for addons is great, but it has a flaw: there are no installed addons in the catalogthis can be solved:
/installed
which just displaysctx.content.addons
with some filteringCatalogFiltered
and adding installed by splitting the Load action intoInstalled(type)
orCatalog(resource_ref)
; this has two extra advantages:catalog -> type
ortype -> catalog
)model.discover
or onlymodel.addons
will receive a certain Loadby creating a fake addonThe text was updated successfully, but these errors were encountered: