Skip to content

fix(gnome-extensions): render missing and unavailable extension data states #1095

Description

@castrojo

Problem

GnomeExtensions.tsx never transitions out of Loading when an extension is absent from the generated array, and calling .find() on the documented unavailable-object payload would throw.

Evidence

For a requested ID not in the payload, data.find(...) returns undefined without setting an error, leaving the component at Loading... permanently. The fetch script also uses a nonzero exit path instead of the standard unavailable payload.

Expected

Handle array, unavailable, and not-found states explicitly; make the fetch script emit a visible unavailable reason without failing the build.

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

    3-clanker-queueWork admitted to the agent-maintained queue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions