Skip to content

The app store has no category filter for templates, although the spec says so #993

Open

Description

@rubenvdlinde

A maker browsing templates in the app store cannot narrow them by category. The spec for the gallery says the filter exists and is tested, but only the Blocks view has one.

Where, at development b90b8c7:

  • openspec/specs/template-catalogue-ui/spec.md:24-44 requires categoryOptions, categoryLabel and filteredTemplates, and a "Filter by category" scenario.
  • src/views/TemplateGallery.vue:45-110 the Templates view lists built-in templates with no filter control.
  • src/views/TemplateGallery.vue:126-136 the only other control there is the GitHub search field.
  • src/views/TemplateGallery.vue:252-256 the Blocks view does have a category filter.
    ### Requirement: Gallery fetches, filters and resolves template screenshots
    `TemplateGallery` SHALL fetch the available templates (`fetchTemplates`),
    expose category filter options and the current filtered set
    (`categoryOptions`, `categoryLabel`, `filteredTemplates`), resolve each
    template's screenshot with a fallback (`resolveScreenshot`), open the clone
    modal (`openClone`), and redirect after a successful clone
    (`onCloneSubmit`, `redirectAfterClone`).
    @e2e exclude retrofit component-contract spec — `categoryOptions`, `categoryLabel`, `filteredTemplates`, `resolveScreenshot`, `openClone`, `onCloneSubmit`, `redirectAfterClone` are component-state contracts verified by Vitest unit tests; gallery filter and clone-redirect integration are covered by the buildiq-template-catalogue Playwright tests
    #### Scenario: Filter by category
    - **WHEN** the user selects a category
    - **THEN** the gallery narrows the visible templates to that category
    #### Scenario: Open clone
    - **WHEN** the user clicks "Use this template"
    - **THEN** the gallery opens the clone dialog seeded with that template

    <template v-if="viewMode === 'templates'">
    <!-- Built-in templates: the application-template records of the
    buildiq register (seeded ones first, then organisation ones). -->
    <section
    class="template-gallery__section"
    data-testid="builtin-templates"
    aria-labelledby="builtin-templates-heading">
    <h2
    id="builtin-templates-heading"
    class="template-gallery__section-title">
    {{ t('buildiq', 'Built-in templates') }}
    </h2>
    <NcNoteCard
    v-if="templatesError"
    type="warning"

The spec's @e2e exclude says Vitest covers these state contracts. TemplateGallery.vue has no categoryOptions or filteredTemplates, and no file under tests/ names them. A second main spec, openspec/specs/openbuild-template-catalogue/spec.md:136-155, still says built-in templates are no longer shown. The gallery shows them again since store-shows-built-in-templates (all tasks ticked, not archived).

Specified fix: openspec/changes/reuse-gallery-categories-and-form-library (REQ-BQGL-001, task T01).

Found by the OpenSpec pass on 27 Sep 2026 and re-read at b90b8c7 on 28 Sep.

Live check: open /apps/buildiq/templates, stay on Templates, and look for a category picker.

Activity

  1. github-actions commented on Sep 27, 2026

    @github-actions
    Contributor

    Thank you for opening this issue! It has been assigned to @rubenvdlinde for review.

    What happens next:

    1. A maintainer will review this issue and determine the appropriate action
    2. If accepted, it may be converted into an OpenSpec change for structured development
    3. You will be notified of any status changes

    Triage labels:

    • triage:accept-feature — accepted as a new feature
    • triage:accept-bugfix — accepted as a bug fix
    • triage:needs-info — more information needed
    • triage:wontfix — will not be addressed
    • triage:duplicate — duplicate of another issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingtriageAwaiting triage

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions