Skip to content

App registry: add compatibility reason messages #329

Description

@sridharkalaibala

Parent: #34

Problem

When an app cannot run on a shop version or edition, the owner should see a clear reason instead of a disabled button with no explanation.

Boundary

Community Edition must continue working fully offline. Use synthetic fixtures only. Do not include live API keys, production customer data, tax IDs, payment details, database dumps, or provider credentials. Do not claim provider support until the related connector is tested and accepted.

Acceptance criteria

  • Define plain-English reason strings for unsupported POS version, Cloud-only app, missing connector runtime and disabled app.
  • Add fixture data for each reason.
  • Confirm existing app listing/install state stays unchanged when no reason exists.

Out of scope

Building the full marketplace UI or changing install permissions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: app platformApp registry, install flow, permissions, extension surfaces, connector runtime contractscommunity editionMust work in the free local/community edition without requiring Posnic CloudenhancementNew feature or requestgood first issueGood for newcomershelp wantedExtra attention is neededneeds designNeeds design notes or acceptance criteria before code PRssize: smallSmall, focused task suitable for a short PR

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions