feat(Giscus): persist discussions via commentId

[idencosmos]

Summary

• Require frontmatter commentId when Giscus uses mapping="specific" so each page persists its own thread
• Clear prior Giscus embeds on SPA navigations before re-injecting; skip injection when the term data is missing
• Keep quartz.layout.ts wrapping Component.Comments behind a commentId guard so only eligible pages render the widget

Layout Example

afterBody: [
  Component.ConditionalRender({
    component: Component.Comments({
      provider: "giscus",
      options: {
        repo: "",
        repoId: "",
        category: "",
        categoryId: "",
        mapping: "specific",
        strict: true,
        reactionsEnabled: true,
        inputPosition: "bottom",
        lang: "ko",
      },
    }),
    condition: ({ fileData }) => Boolean(fileData.frontmatter?.commentId),
  }),
]

In Quartz, afterBody lets a theme append components after the main content. Wrapping Component.Comments in Component.ConditionalRender ensures the Giscus iframe is mounted only when the Markdown frontmatter declares a commentId, which prevents mis-mapping and matches Giscus’ mapping: "specific" requirement.

Why Guard commentId Everywhere

• quartz/components/Comments.tsx blocks the initial component render when the term is missing, preventing Giscus from booting with stale props.
• quartz/components/scripts/comments.inline.ts re-checks during SPA navigations so client-side transitions never resurrect an iframe tied to a different page.
• quartz.layout.ts keeps the widget out of the static HTML build (SSG) entirely unless the page frontmatter opts in, avoiding accidental mounts.
• These layered guards also cover future direct imports of Component.Comments, so no caller can accidentally instantiate the widget without a matching commentId.

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
quartz	✅ Ready (View Log)	Visit Preview	545d65e

[Copilot]

Pull Request Overview

This PR enhances Giscus comments integration by adding support for persistent discussions through commentId mapping and improving SPA navigation handling.

• Adds commentId validation to ensure proper Giscus thread persistence when using mapping="specific"
• Clears previous Giscus embeds during SPA navigation and skips injection when required term data is missing
• Implements layered guards across components to prevent accidental widget instantiation without proper configuration

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
quartz/components/Comments.tsx	Adds commentId validation and term data attribute handling for specific mapping
quartz/components/scripts/comments.inline.ts	Implements cleanup of previous embeds and term validation for SPA navigation

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Setting data-term to undefined will result in the string 'undefined' being set as the attribute value. Use conditional rendering or commentId || undefined to properly omit the attribute when not needed.

Suggested change

	data-term={mapping === "specific" ? commentId : undefined}
	{...(mapping === "specific" && commentId ? { "data-term": commentId } : {})}