Skip to content

Reject Layer Visualization inputs without an applicable model strategy #18

Description

@deem0n

Problem

Layer Visualization accepts a SQL model but findModelApplicableTo: returns nil, leaving an empty browser.

Found during the 2026-09-20 FAMIXNGSQL/Moose 13 compatibility audit.

Implementation scope

Supply an optional SQL layer model with documented catalog/dependency semantics, or explicit capability rejection where an analysis is undefined; ensure users receive an actionable result.

Implementation PR target: deem0n/MooseIDE, in the deem0n fork first. Keep this issue separate from the other v3.0.0 fixes. The PR must explain the previous failure, resulting behavior, compatibility implications, and actual validation.

Acceptance criteria and tests

Applicable SQL fixture; meaningful entities and directed dependencies; empty model; cycles; unsupported input; no artificial OO class traits.

  • Regression tests demonstrate the reported problem and pass with the fix.
  • Relevant existing tests pass; validation environment and limitations are recorded in the PR.
  • A separate implementation PR is linked here and reviewed.
  • Integrated v3.0.0 acceptance is verified before this release blocker is closed.

Release

Part of the v3.0.0 milestone. An open PR is not a completed fix; release qualification is tracked separately.

Implementation

deem0n/MooseIDE#4

Combined qualification: #32. The implementation is available for review; this issue remains open until its integrated release acceptance is verified.

Design decision: implement explicit applicability rejection in the generic MooseIDE browser. No concrete layer strategy is installed for SQL, so inventing Java-like layers would misrepresent the database. A separately designed SQL layering strategy is outside this fix; unsupported inputs are rejected safely.

Activity

  1. added this to the v3.0.0 milestone on Sep 20, 2026
  2. changed the title [-]Add SQL applicability and semantics to Layer Visualization[/-] [+]Reject Layer Visualization inputs without an applicable model strategy[/+] on Sep 20, 2026
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

    No labels
    No labels

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions