docs(ui-kit/angular): flatten component nav, drop enableThreadSubscription from global config - #520
Open
aanshisingh-cometchat wants to merge 2 commits into
Open
docs(ui-kit/angular): flatten component nav, drop enableThreadSubscription from global config#520aanshisingh-cometchat wants to merge 2 commits into
aanshisingh-cometchat wants to merge 2 commits into
Conversation
The Components nav wrapped seven single-page entries in their own accordion — Message Header, Search, Message List, Message Composer, Message Bubble, Message Information and Thread Header — so every one cost a click to reach a single page. Promote all seven to plain page links, and split Pinned & Saved into its two pages rather than keeping a group for them. A group now exists only where it holds more than one page, which is how the React v7 nav already reads. Retitle the search page from "CometChatSearch" to "Search": a flattened entry takes its label from the page's own title, and every sibling uses the human name (Message Header, not CometChatMessageHeader). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016Au57EzdySKicwZPmJThts
Remove the property from the Global Configuration reference: its table row, its own Feature Gates section, and its entries in the components table — which leaves CometChatThreadHeader with no rows at all, so that line goes too. The Feature Gates intro now says two properties, not three. Removing the section broke every link pointing at #enablethreadsubscription, so re-point the four that did. Each of those pages already links the Thread Subscription guide elsewhere, so the anchor is simply dropped and the property named inline. Nest Thread Subscription under Threaded Conversations on Core Features as a subsection rather than a sibling heading: everything else listed there works on install, while thread subscription is off by default and needs an opt-in. The #thread-subscription anchor is unchanged. The flag stays documented in guides/thread-subscription.mdx, which is where an integrator turning the feature on is already reading. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016Au57EzdySKicwZPmJThts
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two independent Angular docs changes, both scoped to
ui-kit/angular/plus the Angular slice ofdocs.json.1. Flatten single-page nav groups
The Components nav wrapped seven single-page entries in their own accordion, so each cost a click to reach one page. All seven are now plain links, and
Pinned & Savedis split into its two pages:The rule is now: a group exists only where it holds more than one page. React v7 already reads this way — it has one accordion to Angular's previous eight.
One title change came with it:
cometchat-search.mdxwastitle: "CometChatSearch". A flattened entry takes its label from the page's own title, so that row would have read "CometChatSearch" while every sibling reads a human name (Message Header, not CometChatMessageHeader). Retitled toSearch, which is what the group was called.2. Drop
enableThreadSubscriptionfrom Global ConfigurationRemoved from the Global Configuration reference — the property table row, its own Feature Gates section, and its entries in the components table. That left
CometChatThreadHeaderwith no rows, so that line went too, and the Feature Gates intro now says two properties rather than three.Removing the section broke every link pointing at
#enablethreadsubscription, so the four that did are re-pointed. Each of those pages already links the Thread Subscription guide elsewhere, so the dead anchor is dropped and the property named inline instead.The flag stays documented in
guides/thread-subscription.mdx— the AI Quick Reference row, the code sample, and the "Turn the gate on" step — which is where someone enabling the feature is already reading.Also on Core Features: Thread Subscription moves from a top-level
##to a###under Threaded Conversations. Everything else on that page works the moment you install the kit; thread subscription is off by default and needs an opt-in, so listing it beside Reactions and Read Receipts promised something the reader wouldn't get. The#thread-subscriptionanchor is unchanged, and this matches how Pinned and Saved Messages already nests### App Settings.Verification
mint devand checked each changed page in the browser.<h2 id="threaded-conversations">→<h3 id="thread-subscription">, and zero occurrences ofenableThreadSubscriptionon the Global Configuration page.docs.jsonresolve to real files;docs.jsonre-parses as valid JSON.global-config#enablethreadsubscriptionreference remains anywhere in the repo.Follow-ups, not in this PR
ui-kit/android/core-features.mdx:186still has## Thread Subscriptionas a top-level sibling, and Android's pin/save section splits differently from Angular's. Worth aligning the two.voice-note-bubblehas no Angular page. React documents it and the component ships in the Angular kit (projects/cometchat-uikit/src/lib/components/cometchat-voice-note-bubble), but there's no.mdxfor it.cometchat-on 43 of 45 component pages; React uses it on none. Aligning would need 43 renames plus redirects, so it belongs in its own PR.🤖 Generated with Claude Code
https://claude.ai/code/session_016Au57EzdySKicwZPmJThts