Skip to content

Community app dependency links use the official store route #2194

Description

@lucasilverentand

Codex created this issue after verifying the behavior against the current UI source and a community app store.

Reproduction

  1. Add a community app store containing app example-store-manager.
  2. Give that app a manifest dependency on another app in the same store, such as example-store-service.
  3. Open the manager app through /community-app-store/example-store/example-store-manager.
  4. Select the dependency in the Requires section.

Current behavior

The dependency link navigates to /app-store/example-store-service, which fails because the app is not in the official store.

packages/ui/src/modules/app-store/app-page/dependencies.tsx hardcodes /app-store/${app.id}. select-dependencies-dialog.tsx contains the same route and a TODO noting that community apps need a different destination.

Expected behavior

When app.appStoreId is not umbrel-app-store, dependency links should navigate to:

/community-app-store/${app.appStoreId}/${app.id}

Official-store dependencies should continue using /app-store/${app.id}. The same route selection should be shared by the Requires section and dependency-selection dialog.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions