import { describe, expect, it } from "vitest";

import { isEnforceableHtmlEquivalent } from "./raw-html-canonical.js";

describe("isEnforceableHtmlEquivalent — library-agnostic enforcement gate", () => {
  it("always enforces low-frequency semantic tags for any canonical name", () => {
    // Agnostic already: a custom-named component on a semantic tag.
    expect(isEnforceableHtmlEquivalent({ tag: "textarea", canonical: "AcmeTextArea" })).toBe(true);
    expect(isEnforceableHtmlEquivalent({ tag: "dialog", canonical: "Modal" })).toBe(true);
  });

  it("enforces an EXPLICITLY-declared button mapping against ANY component name (agnostic)", () => {
    // The fix: @acme/ui's differently-named canonical button now fires on a raw
    // <button>, not only the curated built-in "Button".
    expect(
      isEnforceableHtmlEquivalent({ tag: "button", canonical: "AcmeButton", explicit: true })
    ).toBe(true);
    expect(isEnforceableHtmlEquivalent({ tag: "a", canonical: "AcmeLink", explicit: true })).toBe(
      true
    );
  });

  it("keeps the built-in agreement check for INFERRED button mappings (flood guard)", () => {
    // No `explicit` provenance → an inferred htmlEquivalent must still agree with
    // the curated canonical. This is the <button> → Chip flood class (#229).
    expect(isEnforceableHtmlEquivalent({ tag: "button", canonical: "Chip" })).toBe(false);
    // Agreement (name === curated) still fires without an explicit flag.
    expect(isEnforceableHtmlEquivalent({ tag: "button", canonical: "Button" })).toBe(true);
  });

  it("NEVER enforces generic containers, even when explicitly declared", () => {
    // The load-bearing flood guard: an explicit div/span declaration must not
    // turn every container into a bespoke re-implementation.
    expect(isEnforceableHtmlEquivalent({ tag: "div", canonical: "MyCard", explicit: true })).toBe(
      false
    );
    expect(isEnforceableHtmlEquivalent({ tag: "span", canonical: "MyBadge", explicit: true })).toBe(
      false
    );
  });
});