g-comments 0.2.0 → 0.2.2

package/CHANGELOG.md

@@ -6,6 +6,25 @@ All notable changes to `g-comments` are listed here. The format follows
 
 ## [Unreleased]
 
+## [0.2.2] - 2026-10-20
+
+### Changed
+
+- Classic topics (no nested replies) read the way the forum shows them: one
+  linear list, with a "Replying to @user" link on comments that answer another
+  one. New replies land in the list instead of under their parent. Needs
+  discourse-comments f6312bf or later for the server side.
+
+## [0.2.1] - 2026-10-20
+
+### Changed
+
+- The default stylesheet lives in the `gc-defaults` cascade layer and a forum
+  theme's CSS is imported into `gc-forum`, so site CSS beats the forum's and the
+  forum's beats the defaults regardless of load order or specificity. The forum
+  stylesheet is no longer a `<link>`: it is an `@import … layer(gc-forum)` in
+  the installed `<style>`.
+
 ## [0.2.0] - 2026-10-20
 
 ### Added

package/README.md

@@ -128,15 +128,22 @@ Also available: `Comments.Meta` (author, badges, permalink time),
 `Comments.DevPanel`. The `List` render function is reused for replies at every
 depth, and `Item` keeps the inline reply, edit, report and delete panels.
 
+## Classic topics
+
+A forum without nested replies (or a topic switched to classic mode) reads as
+one linear list in posting order, like the forum itself: a comment that answers
+another carries a "Replying to @user" link instead of being nested under it,
+and `thread.nested` is `false`.
+
 ## Styling
 
 `g-comments/styles.css` styles everything under the widget root
 (`.gc-root.gc-root--styled`); nothing outside it is touched. Class names follow
 BEM (`gc-comment`, `gc-comment__body`, `gc-composer--replying`,
 `gc-button--primary`, …) and stay in place with `unstyled`, which only drops
-`gc-root--styled`. Selectors carry one class of specificity, so your own class
-rules win when loaded after the stylesheet. Cooked comment HTML is wrapped in
-`.gc-prose`.
+`gc-root--styled`. The rules live in the `gc-defaults` cascade layer, so your
+own (unlayered) CSS wins whatever its order or specificity. Cooked comment HTML
+is wrapped in `.gc-prose`.
 
 `appearance.elements` adds class names: `root`, `header`, `count`, `sort`,
 `signIn`, `composer`, `textarea`, `toolbar`, `list`, `comment`, `avatar`,
@@ -191,14 +198,15 @@ element's shadow root. Three things arrive:
   `--gc-forum-font-monospace` carry the stacks, and `@font-face` rules are
   added to the page for fonts the forum serves.
 - **Theme CSS.** The default theme's "Embedded CSS" (Admin → Customize →
-  Themes → Edit CSS/HTML → Embedded) is loaded as a stylesheet, so forum
-  admins can style the `gc-*` classes without touching the site.
-
-Precedence: tokens you set (`appearance.variables`, or `--gc-*` on the root
-or an ancestor) win over the forum's, which win over the defaults. The forum's
-stylesheet is appended after the page's, so plain CSS rules tie-break in the
-forum's favour; out-specify them (`.blog .gc-comment`) where the site must
-win. `useForumTheme()` returns the same data for sites that style their own
+  Themes → Edit CSS/HTML → Embedded) is imported into the `gc-forum` cascade
+  layer, so forum admins can style the `gc-*` classes without touching the
+  site.
+
+Precedence, for tokens and for plain CSS alike: what a component sets
+(`appearance`) beats the site's own CSS and `--gc-*` values, which beat the
+forum's, which beat the defaults. Site CSS is unlayered and the forum's sits in
+`gc-forum` above `gc-defaults`, so no ordering or specificity tricks are
+needed. `useForumTheme()` returns the same data for sites that style their own
 UI after the forum.
 
 ## Custom elements (no framework)
@@ -280,8 +288,11 @@ discourse-comments::part(gc-comment--pinned) {
 `unstyled` drops the default stylesheet's effect (the classes and parts stay),
 `theme="inherit"` derives the neutral colours from the page's text colour, and
 `theme="forum"` loads the forum's palettes, fonts and theme CSS into the shadow
-root (see "Use the forum's look"). The count element has no styles of its own
-and inherits the page's font.
+root (see "Use the forum's look"). Tokens set on the element or an ancestor
+reach the widget by inheritance, which a forum stylesheet that sets `--gc-*`
+on `.gc-root` would override; with `theme="forum"`, set your tokens on
+`discourse-comments::part(gc-root)` instead, which always wins. The count
+element has no styles of its own and inherits the page's font.
 
 `defineElements({ comments: "my-comments", count: "my-count" })` registers the
 same elements under other names; names that are already defined are left

package/dist/{chunk-WACVXJHD.js → chunk-EWWBVJ2B.js}

@@ -2392,7 +2392,7 @@ var CommentThread = class {
       if (!insertable(comment) || this.#deletedAt.has(comment.id)) {
         continue;
       }
-      const parentNumber = comment.reply_to?.number;
+      const parentNumber = this.#state.thread.nested ? comment.reply_to?.number : void 0;
       if (parentNumber === void 0) {
         if (me !== null && comment.author?.id === me) {
           tree = insertRoot(tree, comment, rootPosition(sort));
@@ -2470,7 +2470,7 @@ var CommentThread = class {
     this.#record({ kind: "comments", comments: [comment], insertable: /* @__PURE__ */ new Set([comment.id]), ticket });
     const sort = this.#state.sort;
     let comments = this.#state.comments;
-    if (replyTo !== void 0) {
+    if (replyTo !== void 0 && this.#state.thread.nested) {
       comments = insertReply(comments, replyTo, comment, replyPosition(sort), { bumpCounts: true }) ?? comments;
     } else {
       comments = insertRoot(comments, comment, rootPosition(sort));
@@ -3063,6 +3063,6 @@ function createTranslator(locale, overrides = {}) {
   };
 }
 
-export { CommentsError, PACKAGE_NAME, STORAGE_PREFIX, clientRegistry, createClient, createClientRegistry, createComposerTimer, createTranslator, currentUrlWithoutHash, defaultPageUrl, en, encodeRef, findComment, isCommentsError, isVirtualThread, locales, memoryStorage, normalizeForum, ptBR, resolveLocale };
-//# sourceMappingURL=chunk-WACVXJHD.js.map
-//# sourceMappingURL=chunk-WACVXJHD.js.map
+export { CommentsError, PACKAGE_NAME, STORAGE_PREFIX, clientRegistry, createClient, createClientRegistry, createComposerTimer, createTranslator, currentUrlWithoutHash, defaultPageUrl, en, encodeRef, findByNumber, findComment, isCommentsError, isVirtualThread, locales, memoryStorage, normalizeForum, ptBR, resolveLocale };
+//# sourceMappingURL=chunk-EWWBVJ2B.js.map
+//# sourceMappingURL=chunk-EWWBVJ2B.js.map