docs(ui-kit/angular): add scoped Angular v5 LLM docs index (ENG-38204) by shagundeogharkar · Pull Request #471 · cometchat/docs

shagundeogharkar · 2026-08-17T13:51:27Z

What & why

Part of ENG-38204 (Angular skills — UI Kit + SDK). That ticket's blocking prerequisite is a scoped llms.txt-style index for Angular, because the skills pack is docs-maximal: it builds features from the official task guides and compares its output against them. Without a scoped index there is no way for an agent to discover which guides exist, so it silently falls back to component-wiring and loses the guide-first completeness check.

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index covering all 91 v5 pages as .md twins, in 13 sections. It mirrors the shape of ui-kit/react/llms-react-v7.mdx (currently on branch docs/react-v7-feature-guides, not yet on main).

No Angular SDK index is needed. The ticket asks for two indexes, but Angular consumes the same @cometchat/chat-sdk-javascript@4 as React, and the existing sdk/javascript/llms-javascript-v4.mdx is framework-agnostic — Angular inherits it unchanged.

Changes

New — `ui-kit/angular/llms-angular-v5.mdx`

Unlisted, NOT hidden. Deliberately omitted from docs.json navigation so it never appears in the human sidebar, but it still builds, serves its .md twin, and stays indexed. hidden: true was not used because Mintlify auto-applies noindex to hidden pages, which would drop this page from search and from the auto-generated global llms.txt — defeating the purpose. docs.json is untouched, so there are no navigation refs to break and no redirects required.
Scoped to v5 only. The 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces.
Angular-specific framing that the React index has no equivalent for: kebab-case selectors in templates (<cometchat-conversations>), @Input() rather than props, content-projection / TemplateRef rather than render props, and environment config in src/environments/environment.ts rather than .env.
Section spine: getting started · core & configuration · theming & customization · five component groups · Task guides (recipes) (17 entries) · framework recipes · migration.

Fixes — four content defects surfaced while building the index

Three pages shipped with no frontmatter at all, despite being present in docs.json navigation, so they render untitled on the live site. Added title/description per house style (cf. api-reference/chat-state-service.mdx), and removed the two leading H1s that would now duplicate the frontmatter title:

File	Was	Now
`api-reference/formatter-config-service.mdx`	no frontmatter	`title: "Formatter Config Service"`
`api-reference/rich-text-editor-service.mdx`	no frontmatter, leading `# RichTextEditorService API Reference`	`title: "Rich Text Editor Service"`
`guides/rich-text-formatting.mdx`	no frontmatter, leading `# Rich Text Formatting Guide`	`title: "Rich Text Formatting"`

overview.mdx — "AI Integration Quick Reference" listed incomplete peer deps.

	Value
Was	`@cometchat/chat-sdk-javascript`, `dompurify`
Now	`@cometchat/chat-sdk-javascript`, `@cometchat/cards-angular`, `dompurify`

Ground truth (verified against the shipped package)

The peer-dep fix was confirmed against the published package, not inferred:

$ npm view @cometchat/chat-uikit-angular@5.1.0 peerDependencies
{
"dompurify": "^3.0.0",
"@angular/core": ">=17.0.0 <22.0.0",
"@angular/common": ">=17.0.0 <22.0.0",
"@cometchat/cards-angular": "^1.0.0", ← undocumented
"@cometchat/chat-sdk-javascript": "^4.1.13",
"@cometchat/calls-sdk-javascript": "^5.0.3"
}

@cometchat/cards-angular was added between 5.0.3 and 5.1.0 (latest is 5.1.0; there is no v6 line). Anyone following the docs today gets an incomplete install.

Not fixed here — needs an owner decision

The same overview.mdx accordion states:

| Angular | v18, v19, v20, v21, v22 (v22 requires Node.js 24+) |

But the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0":

v22 is excluded — npm install @cometchat/chat-uikit-angular@^5 on an Angular 22 project hard-fails with ERESOLVE. The docs currently advertise a version where install is impossible.
v17 is supported but undocumented.

So either the docs or the kit's peer range is wrong. That is a support-policy call for the UI Kit owners, not a typo, so this PR leaves the line untouched and flags it instead. It also blocks the Angular core skill, which has to state a supported range.

Checklist

Branch name follows the naming convention (docs/angular-v5-llms-index)
docs.json untouched — no nav refs changed, no redirects needed
All 91 links generated from the actual ui-kit/angular file tree, with page titles read from each file's frontmatter
Peer-dep change verified against the published npm package
npx mintlify dev not yet run — before merge, please confirm the page builds (a "not in navigation" warning is expected and intended) and that /ui-kit/angular/llms-angular-v5.md resolves as raw Markdown. The design depends on that twin being fetchable.

Follow-ups (not in this PR)

Quick Reference accordions on the 43 components/cometchat-*.mdx pages. The index tells agents each .md twin carries input/output names, types and defaults. That holds for guides/ and integration.mdx, but the component pages have no accordion yet, so the promise is currently partial. The React equivalent added these across 56 files in the same branch; for Angular it is deliberately split out as a separate, mechanical PR.
React's own indexes are still unmerged (docs/react-v7-feature-guides, docs/js-sdk-llms-index). Merging this one puts Angular's index in production while React's stays on a preview deploy — worth deciding whether those two should land as well, since the React skills pack currently documents .mintlify.site preview URLs as its docs base.

@input

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index of all 91 v5 pages as .md twins, for AI coding agents. Mirrors the shape of ui-kit/react/llms-react-v7.mdx (branch docs/react-v7-feature-guides). - Unlisted, NOT hidden: omitted from docs.json navigation so it never shows in the human sidebar, but still built, served as a .md twin, and indexed. Using `hidden: true` would auto-apply noindex and drop it from search + the global llms.txt, which defeats the purpose. docs.json is deliberately untouched. - Scoped to v5 only; the 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces. - Angular-specific framing the React index has no equivalent for: kebab-case selectors, @input() rather than props, content-projection/TemplateRef rather than render props, and env config in src/environments/environment.ts. Also fixes four content defects surfaced while building the index: - api-reference/formatter-config-service.mdx, api-reference/ rich-text-editor-service.mdx and guides/rich-text-formatting.mdx shipped with NO frontmatter at all despite being in docs.json navigation, so they rendered untitled. Adds title/description per house style (see api-reference/chat-state-service.mdx) and drops the two leading H1s that would now duplicate the frontmatter title. - overview.mdx "AI Integration Quick Reference" listed peer deps as @cometchat/chat-sdk-javascript + dompurify, missing @cometchat/cards-angular@^1.0.0 which @cometchat/chat-uikit-angular@5.1.0 added. Verified against the published package. NOT fixed here, needs an owner decision: the same accordion claims Angular "v18, v19, v20, v21, v22" but the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0" — v22 is excluded (install hard-fails with ERESOLVE) and v17 is supported but undocumented. Either the docs or the peer range is wrong; that is a support-policy call, not a typo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mintlify · 2026-08-17T13:51:30Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cometchat	🟢 Ready	View Preview	Aug 17, 2026, 1:55 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

shagundeogharkar · 2026-08-19T13:16:21Z

Superseded by #475 — this branch is merged into docs/angular-v5-skills, which carries the same commits plus the remaining Angular docs work (AI Integration Quick Reference accordions across the 43 component pages). Keeping it as one PR gives a single Mintlify preview covering every change. Branch left in place; nothing lost.

Flutter was the only platform with none. On the skills-v5-temp base, react has 128 Quick References and 3 llms indexes, android 112/2, angular 81/1, react-native 56/2, ios 34/2 - and flutter 0 and 0. This closes the index half. Structure and conventions follow the reference PRs for the same feature: cometchat#446 (React v7), cometchat#466 (JS SDK), cometchat#471 (Angular v5), cometchat#476 (React Native). Unlisted rather than hidden, for the reason those PRs give: in Mintlify hidden auto-applies noindex, which would drop the page from search and from the auto global llms.txt - and the whole point is that an agent can discover it. Not registered in docs.json, same as every prior index. ui-kit/flutter/llms-flutter-v6.mdx 70 links, all 54 UI Kit pages sdk/flutter/llms-flutter-v5.mdx 58 links, all 52 SDK pages Both are 100 percent page coverage with zero dead links, verified by resolving every href against the tree. The Platform rules section is the part that carries real weight, and every claim in it was verified against cometchat_chat_uikit 6.1.0 rather than recalled: - TWO barrels with different surfaces. Chat widgets do not resolve from the calls barrel and vice versa, so a screen showing both imports both. This is the most common Flutter-specific compile failure. - Lists need a bounded box or layout throws at render, not at build. - Kit widgets paint their own surface; the app ThemeData does not reach inside. - Theming is ThemeExtension, and registering on only one of light/dark silently leaves the other on kit defaults. - v5's CometChatUIKit.getDataSource() is gone; v6 uses MessageTemplateUtils. - Custom message types need addTemplate, not templates - templates only registers the bubble and the message is filtered out before it can render, with no error. A hand-rolled MessagesRequestBuilder does not help because the list always overrides uid/guid/types/categories on it. - Messages sent with CometChat.send*Message must emit ccMessageSent or a mounted list never shows them. - SDK: onSuccess AND onError are both required - compile-checked, omitting onError is missing_required_argument. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…ent pages Flutter had 0 of these while react has 128, android 112, angular 81, react-native 56 and ios 34. This closes the UI Kit half. Format follows the reference PRs (cometchat#446, cometchat#466, cometchat#471, cometchat#476): an Accordion straight after the frontmatter, a Field/Value table, and rows that let an agent decide whether the page is worth opening at all. Generated from the compiler-verified prop tables rather than hand-written, so every prop named here provably exists on the widget and the row cannot drift from the kit on the next release. 35 in-page anchors, all resolving. Two rows are Flutter-specific and are the reason a generic template would not have done: - Import carries the RIGHT BARREL per widget. Calling widgets resolve only from cometchat_calls_uikit.dart, so call-buttons, incoming-call, outgoing-call and call-logs also get an explicit Barrel row saying so. Importing a calling widget from the chat barrel is the most common Flutter compile failure and no other platform has this split. - Layout warns that list widgets fill their parent and need an Expanded or a sized box, because the failure is an unbounded-height throw at render rather than a build error. Plus the two traps found by building on the kit: message-list carries the addTemplate-not-templates rule, and message-composer carries the ccMessageSent requirement for messages sent outside it. Classification is by TYPE, not name, after three passes got it wrong: messagesRequestBuilder ends in Builder but is data, hideThreadView ends in View but is a bool toggle, headerView is a HeaderFooterBuilder typedef with neither Widget nor Function in its name, and onError is typed OnError? so only the on-plus-capital convention identifies it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

shagundeogharkar · 2026-08-17T13:51:27Z

What & why

Part of ENG-38204 (Angular skills — UI Kit + SDK). That ticket's blocking prerequisite is a scoped llms.txt-style index for Angular, because the skills pack is docs-maximal: it builds features from the official task guides and compares its output against them. Without a scoped index there is no way for an agent to discover which guides exist, so it silently falls back to component-wiring and loses the guide-first completeness check.

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index covering all 91 v5 pages as .md twins, in 13 sections. It mirrors the shape of ui-kit/react/llms-react-v7.mdx (currently on branch docs/react-v7-feature-guides, not yet on main).

No Angular SDK index is needed. The ticket asks for two indexes, but Angular consumes the same @cometchat/chat-sdk-javascript@4 as React, and the existing sdk/javascript/llms-javascript-v4.mdx is framework-agnostic — Angular inherits it unchanged.

Changes

New — `ui-kit/angular/llms-angular-v5.mdx`

Unlisted, NOT hidden. Deliberately omitted from docs.json navigation so it never appears in the human sidebar, but it still builds, serves its .md twin, and stays indexed. hidden: true was not used because Mintlify auto-applies noindex to hidden pages, which would drop this page from search and from the auto-generated global llms.txt — defeating the purpose. docs.json is untouched, so there are no navigation refs to break and no redirects required.
Scoped to v5 only. The 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces.
Angular-specific framing that the React index has no equivalent for: kebab-case selectors in templates (<cometchat-conversations>), @Input() rather than props, content-projection / TemplateRef rather than render props, and environment config in src/environments/environment.ts rather than .env.
Section spine: getting started · core & configuration · theming & customization · five component groups · Task guides (recipes) (17 entries) · framework recipes · migration.

Fixes — four content defects surfaced while building the index

Three pages shipped with no frontmatter at all, despite being present in docs.json navigation, so they render untitled on the live site. Added title/description per house style (cf. api-reference/chat-state-service.mdx), and removed the two leading H1s that would now duplicate the frontmatter title:

File	Was	Now
`api-reference/formatter-config-service.mdx`	no frontmatter	`title: "Formatter Config Service"`
`api-reference/rich-text-editor-service.mdx`	no frontmatter, leading `# RichTextEditorService API Reference`	`title: "Rich Text Editor Service"`
`guides/rich-text-formatting.mdx`	no frontmatter, leading `# Rich Text Formatting Guide`	`title: "Rich Text Formatting"`

overview.mdx — "AI Integration Quick Reference" listed incomplete peer deps.

	Value
Was	`@cometchat/chat-sdk-javascript`, `dompurify`
Now	`@cometchat/chat-sdk-javascript`, `@cometchat/cards-angular`, `dompurify`

Ground truth (verified against the shipped package)

The peer-dep fix was confirmed against the published package, not inferred:

$ npm view @cometchat/chat-uikit-angular@5.1.0 peerDependencies
{
"dompurify": "^3.0.0",
"@angular/core": ">=17.0.0 <22.0.0",
"@angular/common": ">=17.0.0 <22.0.0",
"@cometchat/cards-angular": "^1.0.0", ← undocumented
"@cometchat/chat-sdk-javascript": "^4.1.13",
"@cometchat/calls-sdk-javascript": "^5.0.3"
}

@cometchat/cards-angular was added between 5.0.3 and 5.1.0 (latest is 5.1.0; there is no v6 line). Anyone following the docs today gets an incomplete install.

Not fixed here — needs an owner decision

The same overview.mdx accordion states:

| Angular | v18, v19, v20, v21, v22 (v22 requires Node.js 24+) |

But the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0":

v22 is excluded — npm install @cometchat/chat-uikit-angular@^5 on an Angular 22 project hard-fails with ERESOLVE. The docs currently advertise a version where install is impossible.
v17 is supported but undocumented.

So either the docs or the kit's peer range is wrong. That is a support-policy call for the UI Kit owners, not a typo, so this PR leaves the line untouched and flags it instead. It also blocks the Angular core skill, which has to state a supported range.

Checklist

Branch name follows the naming convention (docs/angular-v5-llms-index)
docs.json untouched — no nav refs changed, no redirects needed
All 91 links generated from the actual ui-kit/angular file tree, with page titles read from each file's frontmatter
Peer-dep change verified against the published npm package
npx mintlify dev not yet run — before merge, please confirm the page builds (a "not in navigation" warning is expected and intended) and that /ui-kit/angular/llms-angular-v5.md resolves as raw Markdown. The design depends on that twin being fetchable.

Follow-ups (not in this PR)

Quick Reference accordions on the 43 components/cometchat-*.mdx pages. The index tells agents each .md twin carries input/output names, types and defaults. That holds for guides/ and integration.mdx, but the component pages have no accordion yet, so the promise is currently partial. The React equivalent added these across 56 files in the same branch; for Angular it is deliberately split out as a separate, mechanical PR.
React's own indexes are still unmerged (docs/react-v7-feature-guides, docs/js-sdk-llms-index). Merging this one puts Angular's index in production while React's stays on a preview deploy — worth deciding whether those two should land as well, since the React skills pack currently documents .mintlify.site preview URLs as its docs base.

@input

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index of all 91 v5 pages as .md twins, for AI coding agents. Mirrors the shape of ui-kit/react/llms-react-v7.mdx (branch docs/react-v7-feature-guides). - Unlisted, NOT hidden: omitted from docs.json navigation so it never shows in the human sidebar, but still built, served as a .md twin, and indexed. Using `hidden: true` would auto-apply noindex and drop it from search + the global llms.txt, which defeats the purpose. docs.json is deliberately untouched. - Scoped to v5 only; the 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces. - Angular-specific framing the React index has no equivalent for: kebab-case selectors, @input() rather than props, content-projection/TemplateRef rather than render props, and env config in src/environments/environment.ts. Also fixes four content defects surfaced while building the index: - api-reference/formatter-config-service.mdx, api-reference/ rich-text-editor-service.mdx and guides/rich-text-formatting.mdx shipped with NO frontmatter at all despite being in docs.json navigation, so they rendered untitled. Adds title/description per house style (see api-reference/chat-state-service.mdx) and drops the two leading H1s that would now duplicate the frontmatter title. - overview.mdx "AI Integration Quick Reference" listed peer deps as @cometchat/chat-sdk-javascript + dompurify, missing @cometchat/cards-angular@^1.0.0 which @cometchat/chat-uikit-angular@5.1.0 added. Verified against the published package. NOT fixed here, needs an owner decision: the same accordion claims Angular "v18, v19, v20, v21, v22" but the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0" — v22 is excluded (install hard-fails with ERESOLVE) and v17 is supported but undocumented. Either the docs or the peer range is wrong; that is a support-policy call, not a typo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mintlify · 2026-08-17T13:51:30Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cometchat	🟢 Ready	View Preview	Aug 17, 2026, 1:55 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

shagundeogharkar · 2026-08-19T13:16:21Z

Superseded by #475 — this branch is merged into docs/angular-v5-skills, which carries the same commits plus the remaining Angular docs work (AI Integration Quick Reference accordions across the 43 component pages). Keeping it as one PR gives a single Mintlify preview covering every change. Branch left in place; nothing lost.

Flutter was the only platform with none. On the skills-v5-temp base, react has 128 Quick References and 3 llms indexes, android 112/2, angular 81/1, react-native 56/2, ios 34/2 - and flutter 0 and 0. This closes the index half. Structure and conventions follow the reference PRs for the same feature: cometchat#446 (React v7), cometchat#466 (JS SDK), cometchat#471 (Angular v5), cometchat#476 (React Native). Unlisted rather than hidden, for the reason those PRs give: in Mintlify hidden auto-applies noindex, which would drop the page from search and from the auto global llms.txt - and the whole point is that an agent can discover it. Not registered in docs.json, same as every prior index. ui-kit/flutter/llms-flutter-v6.mdx 70 links, all 54 UI Kit pages sdk/flutter/llms-flutter-v5.mdx 58 links, all 52 SDK pages Both are 100 percent page coverage with zero dead links, verified by resolving every href against the tree. The Platform rules section is the part that carries real weight, and every claim in it was verified against cometchat_chat_uikit 6.1.0 rather than recalled: - TWO barrels with different surfaces. Chat widgets do not resolve from the calls barrel and vice versa, so a screen showing both imports both. This is the most common Flutter-specific compile failure. - Lists need a bounded box or layout throws at render, not at build. - Kit widgets paint their own surface; the app ThemeData does not reach inside. - Theming is ThemeExtension, and registering on only one of light/dark silently leaves the other on kit defaults. - v5's CometChatUIKit.getDataSource() is gone; v6 uses MessageTemplateUtils. - Custom message types need addTemplate, not templates - templates only registers the bubble and the message is filtered out before it can render, with no error. A hand-rolled MessagesRequestBuilder does not help because the list always overrides uid/guid/types/categories on it. - Messages sent with CometChat.send*Message must emit ccMessageSent or a mounted list never shows them. - SDK: onSuccess AND onError are both required - compile-checked, omitting onError is missing_required_argument. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…ent pages Flutter had 0 of these while react has 128, android 112, angular 81, react-native 56 and ios 34. This closes the UI Kit half. Format follows the reference PRs (cometchat#446, cometchat#466, cometchat#471, cometchat#476): an Accordion straight after the frontmatter, a Field/Value table, and rows that let an agent decide whether the page is worth opening at all. Generated from the compiler-verified prop tables rather than hand-written, so every prop named here provably exists on the widget and the row cannot drift from the kit on the next release. 35 in-page anchors, all resolving. Two rows are Flutter-specific and are the reason a generic template would not have done: - Import carries the RIGHT BARREL per widget. Calling widgets resolve only from cometchat_calls_uikit.dart, so call-buttons, incoming-call, outgoing-call and call-logs also get an explicit Barrel row saying so. Importing a calling widget from the chat barrel is the most common Flutter compile failure and no other platform has this split. - Layout warns that list widgets fill their parent and need an Expanded or a sized box, because the failure is an unbounded-height throw at render rather than a build error. Plus the two traps found by building on the kit: message-list carries the addTemplate-not-templates rule, and message-composer carries the ccMessageSent requirement for messages sent outside it. Classification is by TYPE, not name, after three passes got it wrong: messagesRequestBuilder ends in Builder but is data, hideThreadView ends in View but is a bool toggle, headerView is a HeaderFooterBuilder typedef with neither Widget nor Function in its name, and onError is typed OnError? so only the on-plus-capital convention identifies it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

shagundeogharkar · 2026-08-17T13:51:27Z

What & why

Part of ENG-38204 (Angular skills — UI Kit + SDK). That ticket's blocking prerequisite is a scoped llms.txt-style index for Angular, because the skills pack is docs-maximal: it builds features from the official task guides and compares its output against them. Without a scoped index there is no way for an agent to discover which guides exist, so it silently falls back to component-wiring and loses the guide-first completeness check.

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index covering all 91 v5 pages as .md twins, in 13 sections. It mirrors the shape of ui-kit/react/llms-react-v7.mdx (currently on branch docs/react-v7-feature-guides, not yet on main).

No Angular SDK index is needed. The ticket asks for two indexes, but Angular consumes the same @cometchat/chat-sdk-javascript@4 as React, and the existing sdk/javascript/llms-javascript-v4.mdx is framework-agnostic — Angular inherits it unchanged.

Changes

New — `ui-kit/angular/llms-angular-v5.mdx`

Unlisted, NOT hidden. Deliberately omitted from docs.json navigation so it never appears in the human sidebar, but it still builds, serves its .md twin, and stays indexed. hidden: true was not used because Mintlify auto-applies noindex to hidden pages, which would drop this page from search and from the auto-generated global llms.txt — defeating the purpose. docs.json is untouched, so there are no navigation refs to break and no redirects required.
Scoped to v5 only. The 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces.
Angular-specific framing that the React index has no equivalent for: kebab-case selectors in templates (<cometchat-conversations>), @Input() rather than props, content-projection / TemplateRef rather than render props, and environment config in src/environments/environment.ts rather than .env.
Section spine: getting started · core & configuration · theming & customization · five component groups · Task guides (recipes) (17 entries) · framework recipes · migration.

Fixes — four content defects surfaced while building the index

Three pages shipped with no frontmatter at all, despite being present in docs.json navigation, so they render untitled on the live site. Added title/description per house style (cf. api-reference/chat-state-service.mdx), and removed the two leading H1s that would now duplicate the frontmatter title:

File	Was	Now
`api-reference/formatter-config-service.mdx`	no frontmatter	`title: "Formatter Config Service"`
`api-reference/rich-text-editor-service.mdx`	no frontmatter, leading `# RichTextEditorService API Reference`	`title: "Rich Text Editor Service"`
`guides/rich-text-formatting.mdx`	no frontmatter, leading `# Rich Text Formatting Guide`	`title: "Rich Text Formatting"`

overview.mdx — "AI Integration Quick Reference" listed incomplete peer deps.

	Value
Was	`@cometchat/chat-sdk-javascript`, `dompurify`
Now	`@cometchat/chat-sdk-javascript`, `@cometchat/cards-angular`, `dompurify`

Ground truth (verified against the shipped package)

The peer-dep fix was confirmed against the published package, not inferred:

$ npm view @cometchat/chat-uikit-angular@5.1.0 peerDependencies
{
"dompurify": "^3.0.0",
"@angular/core": ">=17.0.0 <22.0.0",
"@angular/common": ">=17.0.0 <22.0.0",
"@cometchat/cards-angular": "^1.0.0", ← undocumented
"@cometchat/chat-sdk-javascript": "^4.1.13",
"@cometchat/calls-sdk-javascript": "^5.0.3"
}

@cometchat/cards-angular was added between 5.0.3 and 5.1.0 (latest is 5.1.0; there is no v6 line). Anyone following the docs today gets an incomplete install.

Not fixed here — needs an owner decision

The same overview.mdx accordion states:

| Angular | v18, v19, v20, v21, v22 (v22 requires Node.js 24+) |

But the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0":

v22 is excluded — npm install @cometchat/chat-uikit-angular@^5 on an Angular 22 project hard-fails with ERESOLVE. The docs currently advertise a version where install is impossible.
v17 is supported but undocumented.

So either the docs or the kit's peer range is wrong. That is a support-policy call for the UI Kit owners, not a typo, so this PR leaves the line untouched and flags it instead. It also blocks the Angular core skill, which has to state a supported range.

Checklist

Branch name follows the naming convention (docs/angular-v5-llms-index)
docs.json untouched — no nav refs changed, no redirects needed
All 91 links generated from the actual ui-kit/angular file tree, with page titles read from each file's frontmatter
Peer-dep change verified against the published npm package
npx mintlify dev not yet run — before merge, please confirm the page builds (a "not in navigation" warning is expected and intended) and that /ui-kit/angular/llms-angular-v5.md resolves as raw Markdown. The design depends on that twin being fetchable.

Follow-ups (not in this PR)

Quick Reference accordions on the 43 components/cometchat-*.mdx pages. The index tells agents each .md twin carries input/output names, types and defaults. That holds for guides/ and integration.mdx, but the component pages have no accordion yet, so the promise is currently partial. The React equivalent added these across 56 files in the same branch; for Angular it is deliberately split out as a separate, mechanical PR.
React's own indexes are still unmerged (docs/react-v7-feature-guides, docs/js-sdk-llms-index). Merging this one puts Angular's index in production while React's stays on a preview deploy — worth deciding whether those two should land as well, since the React skills pack currently documents .mintlify.site preview URLs as its docs base.

@input

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index of all 91 v5 pages as .md twins, for AI coding agents. Mirrors the shape of ui-kit/react/llms-react-v7.mdx (branch docs/react-v7-feature-guides). - Unlisted, NOT hidden: omitted from docs.json navigation so it never shows in the human sidebar, but still built, served as a .md twin, and indexed. Using `hidden: true` would auto-apply noindex and drop it from search + the global llms.txt, which defeats the purpose. docs.json is deliberately untouched. - Scoped to v5 only; the 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces. - Angular-specific framing the React index has no equivalent for: kebab-case selectors, @input() rather than props, content-projection/TemplateRef rather than render props, and env config in src/environments/environment.ts. Also fixes four content defects surfaced while building the index: - api-reference/formatter-config-service.mdx, api-reference/ rich-text-editor-service.mdx and guides/rich-text-formatting.mdx shipped with NO frontmatter at all despite being in docs.json navigation, so they rendered untitled. Adds title/description per house style (see api-reference/chat-state-service.mdx) and drops the two leading H1s that would now duplicate the frontmatter title. - overview.mdx "AI Integration Quick Reference" listed peer deps as @cometchat/chat-sdk-javascript + dompurify, missing @cometchat/cards-angular@^1.0.0 which @cometchat/chat-uikit-angular@5.1.0 added. Verified against the published package. NOT fixed here, needs an owner decision: the same accordion claims Angular "v18, v19, v20, v21, v22" but the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0" — v22 is excluded (install hard-fails with ERESOLVE) and v17 is supported but undocumented. Either the docs or the peer range is wrong; that is a support-policy call, not a typo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mintlify · 2026-08-17T13:51:30Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cometchat	🟢 Ready	View Preview	Aug 17, 2026, 1:55 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

shagundeogharkar · 2026-08-19T13:16:21Z

Superseded by #475 — this branch is merged into docs/angular-v5-skills, which carries the same commits plus the remaining Angular docs work (AI Integration Quick Reference accordions across the 43 component pages). Keeping it as one PR gives a single Mintlify preview covering every change. Branch left in place; nothing lost.

Flutter was the only platform with none. On the skills-v5-temp base, react has 128 Quick References and 3 llms indexes, android 112/2, angular 81/1, react-native 56/2, ios 34/2 - and flutter 0 and 0. This closes the index half. Structure and conventions follow the reference PRs for the same feature: cometchat#446 (React v7), cometchat#466 (JS SDK), cometchat#471 (Angular v5), cometchat#476 (React Native). Unlisted rather than hidden, for the reason those PRs give: in Mintlify hidden auto-applies noindex, which would drop the page from search and from the auto global llms.txt - and the whole point is that an agent can discover it. Not registered in docs.json, same as every prior index. ui-kit/flutter/llms-flutter-v6.mdx 70 links, all 54 UI Kit pages sdk/flutter/llms-flutter-v5.mdx 58 links, all 52 SDK pages Both are 100 percent page coverage with zero dead links, verified by resolving every href against the tree. The Platform rules section is the part that carries real weight, and every claim in it was verified against cometchat_chat_uikit 6.1.0 rather than recalled: - TWO barrels with different surfaces. Chat widgets do not resolve from the calls barrel and vice versa, so a screen showing both imports both. This is the most common Flutter-specific compile failure. - Lists need a bounded box or layout throws at render, not at build. - Kit widgets paint their own surface; the app ThemeData does not reach inside. - Theming is ThemeExtension, and registering on only one of light/dark silently leaves the other on kit defaults. - v5's CometChatUIKit.getDataSource() is gone; v6 uses MessageTemplateUtils. - Custom message types need addTemplate, not templates - templates only registers the bubble and the message is filtered out before it can render, with no error. A hand-rolled MessagesRequestBuilder does not help because the list always overrides uid/guid/types/categories on it. - Messages sent with CometChat.send*Message must emit ccMessageSent or a mounted list never shows them. - SDK: onSuccess AND onError are both required - compile-checked, omitting onError is missing_required_argument. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…ent pages Flutter had 0 of these while react has 128, android 112, angular 81, react-native 56 and ios 34. This closes the UI Kit half. Format follows the reference PRs (cometchat#446, cometchat#466, cometchat#471, cometchat#476): an Accordion straight after the frontmatter, a Field/Value table, and rows that let an agent decide whether the page is worth opening at all. Generated from the compiler-verified prop tables rather than hand-written, so every prop named here provably exists on the widget and the row cannot drift from the kit on the next release. 35 in-page anchors, all resolving. Two rows are Flutter-specific and are the reason a generic template would not have done: - Import carries the RIGHT BARREL per widget. Calling widgets resolve only from cometchat_calls_uikit.dart, so call-buttons, incoming-call, outgoing-call and call-logs also get an explicit Barrel row saying so. Importing a calling widget from the chat barrel is the most common Flutter compile failure and no other platform has this split. - Layout warns that list widgets fill their parent and need an Expanded or a sized box, because the failure is an unbounded-height throw at render rather than a build error. Plus the two traps found by building on the kit: message-list carries the addTemplate-not-templates rule, and message-composer carries the ccMessageSent requirement for messages sent outside it. Classification is by TYPE, not name, after three passes got it wrong: messagesRequestBuilder ends in Builder but is data, hideThreadView ends in View but is a bool toggle, headerView is a HeaderFooterBuilder typedef with neither Widget nor Function in its name, and onError is typed OnError? so only the on-plus-capital convention identifies it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

shagundeogharkar · 2026-08-17T13:51:27Z

What & why

Part of ENG-38204 (Angular skills — UI Kit + SDK). That ticket's blocking prerequisite is a scoped llms.txt-style index for Angular, because the skills pack is docs-maximal: it builds features from the official task guides and compares its output against them. Without a scoped index there is no way for an agent to discover which guides exist, so it silently falls back to component-wiring and loses the guide-first completeness check.

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index covering all 91 v5 pages as .md twins, in 13 sections. It mirrors the shape of ui-kit/react/llms-react-v7.mdx (currently on branch docs/react-v7-feature-guides, not yet on main).

No Angular SDK index is needed. The ticket asks for two indexes, but Angular consumes the same @cometchat/chat-sdk-javascript@4 as React, and the existing sdk/javascript/llms-javascript-v4.mdx is framework-agnostic — Angular inherits it unchanged.

Changes

New — `ui-kit/angular/llms-angular-v5.mdx`

Unlisted, NOT hidden. Deliberately omitted from docs.json navigation so it never appears in the human sidebar, but it still builds, serves its .md twin, and stays indexed. hidden: true was not used because Mintlify auto-applies noindex to hidden pages, which would drop this page from search and from the auto-generated global llms.txt — defeating the purpose. docs.json is untouched, so there are no navigation refs to break and no redirects required.
Scoped to v5 only. The 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces.
Angular-specific framing that the React index has no equivalent for: kebab-case selectors in templates (<cometchat-conversations>), @Input() rather than props, content-projection / TemplateRef rather than render props, and environment config in src/environments/environment.ts rather than .env.
Section spine: getting started · core & configuration · theming & customization · five component groups · Task guides (recipes) (17 entries) · framework recipes · migration.

Fixes — four content defects surfaced while building the index

Three pages shipped with no frontmatter at all, despite being present in docs.json navigation, so they render untitled on the live site. Added title/description per house style (cf. api-reference/chat-state-service.mdx), and removed the two leading H1s that would now duplicate the frontmatter title:

File	Was	Now
`api-reference/formatter-config-service.mdx`	no frontmatter	`title: "Formatter Config Service"`
`api-reference/rich-text-editor-service.mdx`	no frontmatter, leading `# RichTextEditorService API Reference`	`title: "Rich Text Editor Service"`
`guides/rich-text-formatting.mdx`	no frontmatter, leading `# Rich Text Formatting Guide`	`title: "Rich Text Formatting"`

overview.mdx — "AI Integration Quick Reference" listed incomplete peer deps.

	Value
Was	`@cometchat/chat-sdk-javascript`, `dompurify`
Now	`@cometchat/chat-sdk-javascript`, `@cometchat/cards-angular`, `dompurify`

Ground truth (verified against the shipped package)

The peer-dep fix was confirmed against the published package, not inferred:

$ npm view @cometchat/chat-uikit-angular@5.1.0 peerDependencies
{
"dompurify": "^3.0.0",
"@angular/core": ">=17.0.0 <22.0.0",
"@angular/common": ">=17.0.0 <22.0.0",
"@cometchat/cards-angular": "^1.0.0", ← undocumented
"@cometchat/chat-sdk-javascript": "^4.1.13",
"@cometchat/calls-sdk-javascript": "^5.0.3"
}

@cometchat/cards-angular was added between 5.0.3 and 5.1.0 (latest is 5.1.0; there is no v6 line). Anyone following the docs today gets an incomplete install.

Not fixed here — needs an owner decision

The same overview.mdx accordion states:

| Angular | v18, v19, v20, v21, v22 (v22 requires Node.js 24+) |

But the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0":

v22 is excluded — npm install @cometchat/chat-uikit-angular@^5 on an Angular 22 project hard-fails with ERESOLVE. The docs currently advertise a version where install is impossible.
v17 is supported but undocumented.

So either the docs or the kit's peer range is wrong. That is a support-policy call for the UI Kit owners, not a typo, so this PR leaves the line untouched and flags it instead. It also blocks the Angular core skill, which has to state a supported range.

Checklist

Branch name follows the naming convention (docs/angular-v5-llms-index)
docs.json untouched — no nav refs changed, no redirects needed
All 91 links generated from the actual ui-kit/angular file tree, with page titles read from each file's frontmatter
Peer-dep change verified against the published npm package
npx mintlify dev not yet run — before merge, please confirm the page builds (a "not in navigation" warning is expected and intended) and that /ui-kit/angular/llms-angular-v5.md resolves as raw Markdown. The design depends on that twin being fetchable.

Follow-ups (not in this PR)

Quick Reference accordions on the 43 components/cometchat-*.mdx pages. The index tells agents each .md twin carries input/output names, types and defaults. That holds for guides/ and integration.mdx, but the component pages have no accordion yet, so the promise is currently partial. The React equivalent added these across 56 files in the same branch; for Angular it is deliberately split out as a separate, mechanical PR.
React's own indexes are still unmerged (docs/react-v7-feature-guides, docs/js-sdk-llms-index). Merging this one puts Angular's index in production while React's stays on a preview deploy — worth deciding whether those two should land as well, since the React skills pack currently documents .mintlify.site preview URLs as its docs base.

@input

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index of all 91 v5 pages as .md twins, for AI coding agents. Mirrors the shape of ui-kit/react/llms-react-v7.mdx (branch docs/react-v7-feature-guides). - Unlisted, NOT hidden: omitted from docs.json navigation so it never shows in the human sidebar, but still built, served as a .md twin, and indexed. Using `hidden: true` would auto-apply noindex and drop it from search + the global llms.txt, which defeats the purpose. docs.json is deliberately untouched. - Scoped to v5 only; the 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces. - Angular-specific framing the React index has no equivalent for: kebab-case selectors, @input() rather than props, content-projection/TemplateRef rather than render props, and env config in src/environments/environment.ts. Also fixes four content defects surfaced while building the index: - api-reference/formatter-config-service.mdx, api-reference/ rich-text-editor-service.mdx and guides/rich-text-formatting.mdx shipped with NO frontmatter at all despite being in docs.json navigation, so they rendered untitled. Adds title/description per house style (see api-reference/chat-state-service.mdx) and drops the two leading H1s that would now duplicate the frontmatter title. - overview.mdx "AI Integration Quick Reference" listed peer deps as @cometchat/chat-sdk-javascript + dompurify, missing @cometchat/cards-angular@^1.0.0 which @cometchat/chat-uikit-angular@5.1.0 added. Verified against the published package. NOT fixed here, needs an owner decision: the same accordion claims Angular "v18, v19, v20, v21, v22" but the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0" — v22 is excluded (install hard-fails with ERESOLVE) and v17 is supported but undocumented. Either the docs or the peer range is wrong; that is a support-policy call, not a typo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mintlify · 2026-08-17T13:51:30Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cometchat	🟢 Ready	View Preview	Aug 17, 2026, 1:55 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

shagundeogharkar · 2026-08-19T13:16:21Z

Superseded by #475 — this branch is merged into docs/angular-v5-skills, which carries the same commits plus the remaining Angular docs work (AI Integration Quick Reference accordions across the 43 component pages). Keeping it as one PR gives a single Mintlify preview covering every change. Branch left in place; nothing lost.

Flutter was the only platform with none. On the skills-v5-temp base, react has 128 Quick References and 3 llms indexes, android 112/2, angular 81/1, react-native 56/2, ios 34/2 - and flutter 0 and 0. This closes the index half. Structure and conventions follow the reference PRs for the same feature: cometchat#446 (React v7), cometchat#466 (JS SDK), cometchat#471 (Angular v5), cometchat#476 (React Native). Unlisted rather than hidden, for the reason those PRs give: in Mintlify hidden auto-applies noindex, which would drop the page from search and from the auto global llms.txt - and the whole point is that an agent can discover it. Not registered in docs.json, same as every prior index. ui-kit/flutter/llms-flutter-v6.mdx 70 links, all 54 UI Kit pages sdk/flutter/llms-flutter-v5.mdx 58 links, all 52 SDK pages Both are 100 percent page coverage with zero dead links, verified by resolving every href against the tree. The Platform rules section is the part that carries real weight, and every claim in it was verified against cometchat_chat_uikit 6.1.0 rather than recalled: - TWO barrels with different surfaces. Chat widgets do not resolve from the calls barrel and vice versa, so a screen showing both imports both. This is the most common Flutter-specific compile failure. - Lists need a bounded box or layout throws at render, not at build. - Kit widgets paint their own surface; the app ThemeData does not reach inside. - Theming is ThemeExtension, and registering on only one of light/dark silently leaves the other on kit defaults. - v5's CometChatUIKit.getDataSource() is gone; v6 uses MessageTemplateUtils. - Custom message types need addTemplate, not templates - templates only registers the bubble and the message is filtered out before it can render, with no error. A hand-rolled MessagesRequestBuilder does not help because the list always overrides uid/guid/types/categories on it. - Messages sent with CometChat.send*Message must emit ccMessageSent or a mounted list never shows them. - SDK: onSuccess AND onError are both required - compile-checked, omitting onError is missing_required_argument. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…ent pages Flutter had 0 of these while react has 128, android 112, angular 81, react-native 56 and ios 34. This closes the UI Kit half. Format follows the reference PRs (cometchat#446, cometchat#466, cometchat#471, cometchat#476): an Accordion straight after the frontmatter, a Field/Value table, and rows that let an agent decide whether the page is worth opening at all. Generated from the compiler-verified prop tables rather than hand-written, so every prop named here provably exists on the widget and the row cannot drift from the kit on the next release. 35 in-page anchors, all resolving. Two rows are Flutter-specific and are the reason a generic template would not have done: - Import carries the RIGHT BARREL per widget. Calling widgets resolve only from cometchat_calls_uikit.dart, so call-buttons, incoming-call, outgoing-call and call-logs also get an explicit Barrel row saying so. Importing a calling widget from the chat barrel is the most common Flutter compile failure and no other platform has this split. - Layout warns that list widgets fill their parent and need an Expanded or a sized box, because the failure is an unbounded-height throw at render rather than a build error. Plus the two traps found by building on the kit: message-list carries the addTemplate-not-templates rule, and message-composer carries the ccMessageSent requirement for messages sent outside it. Classification is by TYPE, not name, after three passes got it wrong: messagesRequestBuilder ends in Builder but is data, hideThreadView ends in View but is a bool toggle, headerView is a HeaderFooterBuilder typedef with neither Widget nor Function in its name, and onError is typed OnError? so only the on-plus-capital convention identifies it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

shagundeogharkar · 2026-08-17T13:51:27Z

What & why

Part of ENG-38204 (Angular skills — UI Kit + SDK). That ticket's blocking prerequisite is a scoped llms.txt-style index for Angular, because the skills pack is docs-maximal: it builds features from the official task guides and compares its output against them. Without a scoped index there is no way for an agent to discover which guides exist, so it silently falls back to component-wiring and loses the guide-first completeness check.

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index covering all 91 v5 pages as .md twins, in 13 sections. It mirrors the shape of ui-kit/react/llms-react-v7.mdx (currently on branch docs/react-v7-feature-guides, not yet on main).

No Angular SDK index is needed. The ticket asks for two indexes, but Angular consumes the same @cometchat/chat-sdk-javascript@4 as React, and the existing sdk/javascript/llms-javascript-v4.mdx is framework-agnostic — Angular inherits it unchanged.

Changes

New — `ui-kit/angular/llms-angular-v5.mdx`

Unlisted, NOT hidden. Deliberately omitted from docs.json navigation so it never appears in the human sidebar, but it still builds, serves its .md twin, and stays indexed. hidden: true was not used because Mintlify auto-applies noindex to hidden pages, which would drop this page from search and from the auto-generated global llms.txt — defeating the purpose. docs.json is untouched, so there are no navigation refs to break and no redirects required.
Scoped to v5 only. The 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces.
Angular-specific framing that the React index has no equivalent for: kebab-case selectors in templates (<cometchat-conversations>), @Input() rather than props, content-projection / TemplateRef rather than render props, and environment config in src/environments/environment.ts rather than .env.
Section spine: getting started · core & configuration · theming & customization · five component groups · Task guides (recipes) (17 entries) · framework recipes · migration.

Fixes — four content defects surfaced while building the index

Three pages shipped with no frontmatter at all, despite being present in docs.json navigation, so they render untitled on the live site. Added title/description per house style (cf. api-reference/chat-state-service.mdx), and removed the two leading H1s that would now duplicate the frontmatter title:

File	Was	Now
`api-reference/formatter-config-service.mdx`	no frontmatter	`title: "Formatter Config Service"`
`api-reference/rich-text-editor-service.mdx`	no frontmatter, leading `# RichTextEditorService API Reference`	`title: "Rich Text Editor Service"`
`guides/rich-text-formatting.mdx`	no frontmatter, leading `# Rich Text Formatting Guide`	`title: "Rich Text Formatting"`

overview.mdx — "AI Integration Quick Reference" listed incomplete peer deps.

	Value
Was	`@cometchat/chat-sdk-javascript`, `dompurify`
Now	`@cometchat/chat-sdk-javascript`, `@cometchat/cards-angular`, `dompurify`

Ground truth (verified against the shipped package)

The peer-dep fix was confirmed against the published package, not inferred:

$ npm view @cometchat/chat-uikit-angular@5.1.0 peerDependencies
{
"dompurify": "^3.0.0",
"@angular/core": ">=17.0.0 <22.0.0",
"@angular/common": ">=17.0.0 <22.0.0",
"@cometchat/cards-angular": "^1.0.0", ← undocumented
"@cometchat/chat-sdk-javascript": "^4.1.13",
"@cometchat/calls-sdk-javascript": "^5.0.3"
}

@cometchat/cards-angular was added between 5.0.3 and 5.1.0 (latest is 5.1.0; there is no v6 line). Anyone following the docs today gets an incomplete install.

Not fixed here — needs an owner decision

The same overview.mdx accordion states:

| Angular | v18, v19, v20, v21, v22 (v22 requires Node.js 24+) |

But the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0":

v22 is excluded — npm install @cometchat/chat-uikit-angular@^5 on an Angular 22 project hard-fails with ERESOLVE. The docs currently advertise a version where install is impossible.
v17 is supported but undocumented.

So either the docs or the kit's peer range is wrong. That is a support-policy call for the UI Kit owners, not a typo, so this PR leaves the line untouched and flags it instead. It also blocks the Angular core skill, which has to state a supported range.

Checklist

Branch name follows the naming convention (docs/angular-v5-llms-index)
docs.json untouched — no nav refs changed, no redirects needed
All 91 links generated from the actual ui-kit/angular file tree, with page titles read from each file's frontmatter
Peer-dep change verified against the published npm package
npx mintlify dev not yet run — before merge, please confirm the page builds (a "not in navigation" warning is expected and intended) and that /ui-kit/angular/llms-angular-v5.md resolves as raw Markdown. The design depends on that twin being fetchable.

Follow-ups (not in this PR)

Quick Reference accordions on the 43 components/cometchat-*.mdx pages. The index tells agents each .md twin carries input/output names, types and defaults. That holds for guides/ and integration.mdx, but the component pages have no accordion yet, so the promise is currently partial. The React equivalent added these across 56 files in the same branch; for Angular it is deliberately split out as a separate, mechanical PR.
React's own indexes are still unmerged (docs/react-v7-feature-guides, docs/js-sdk-llms-index). Merging this one puts Angular's index in production while React's stays on a preview deploy — worth deciding whether those two should land as well, since the React skills pack currently documents .mintlify.site preview URLs as its docs base.

@input

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index of all 91 v5 pages as .md twins, for AI coding agents. Mirrors the shape of ui-kit/react/llms-react-v7.mdx (branch docs/react-v7-feature-guides). - Unlisted, NOT hidden: omitted from docs.json navigation so it never shows in the human sidebar, but still built, served as a .md twin, and indexed. Using `hidden: true` would auto-apply noindex and drop it from search + the global llms.txt, which defeats the purpose. docs.json is deliberately untouched. - Scoped to v5 only; the 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces. - Angular-specific framing the React index has no equivalent for: kebab-case selectors, @input() rather than props, content-projection/TemplateRef rather than render props, and env config in src/environments/environment.ts. Also fixes four content defects surfaced while building the index: - api-reference/formatter-config-service.mdx, api-reference/ rich-text-editor-service.mdx and guides/rich-text-formatting.mdx shipped with NO frontmatter at all despite being in docs.json navigation, so they rendered untitled. Adds title/description per house style (see api-reference/chat-state-service.mdx) and drops the two leading H1s that would now duplicate the frontmatter title. - overview.mdx "AI Integration Quick Reference" listed peer deps as @cometchat/chat-sdk-javascript + dompurify, missing @cometchat/cards-angular@^1.0.0 which @cometchat/chat-uikit-angular@5.1.0 added. Verified against the published package. NOT fixed here, needs an owner decision: the same accordion claims Angular "v18, v19, v20, v21, v22" but the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0" — v22 is excluded (install hard-fails with ERESOLVE) and v17 is supported but undocumented. Either the docs or the peer range is wrong; that is a support-policy call, not a typo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mintlify · 2026-08-17T13:51:30Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cometchat	🟢 Ready	View Preview	Aug 17, 2026, 1:55 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

shagundeogharkar · 2026-08-19T13:16:21Z

Superseded by #475 — this branch is merged into docs/angular-v5-skills, which carries the same commits plus the remaining Angular docs work (AI Integration Quick Reference accordions across the 43 component pages). Keeping it as one PR gives a single Mintlify preview covering every change. Branch left in place; nothing lost.

Flutter was the only platform with none. On the skills-v5-temp base, react has 128 Quick References and 3 llms indexes, android 112/2, angular 81/1, react-native 56/2, ios 34/2 - and flutter 0 and 0. This closes the index half. Structure and conventions follow the reference PRs for the same feature: cometchat#446 (React v7), cometchat#466 (JS SDK), cometchat#471 (Angular v5), cometchat#476 (React Native). Unlisted rather than hidden, for the reason those PRs give: in Mintlify hidden auto-applies noindex, which would drop the page from search and from the auto global llms.txt - and the whole point is that an agent can discover it. Not registered in docs.json, same as every prior index. ui-kit/flutter/llms-flutter-v6.mdx 70 links, all 54 UI Kit pages sdk/flutter/llms-flutter-v5.mdx 58 links, all 52 SDK pages Both are 100 percent page coverage with zero dead links, verified by resolving every href against the tree. The Platform rules section is the part that carries real weight, and every claim in it was verified against cometchat_chat_uikit 6.1.0 rather than recalled: - TWO barrels with different surfaces. Chat widgets do not resolve from the calls barrel and vice versa, so a screen showing both imports both. This is the most common Flutter-specific compile failure. - Lists need a bounded box or layout throws at render, not at build. - Kit widgets paint their own surface; the app ThemeData does not reach inside. - Theming is ThemeExtension, and registering on only one of light/dark silently leaves the other on kit defaults. - v5's CometChatUIKit.getDataSource() is gone; v6 uses MessageTemplateUtils. - Custom message types need addTemplate, not templates - templates only registers the bubble and the message is filtered out before it can render, with no error. A hand-rolled MessagesRequestBuilder does not help because the list always overrides uid/guid/types/categories on it. - Messages sent with CometChat.send*Message must emit ccMessageSent or a mounted list never shows them. - SDK: onSuccess AND onError are both required - compile-checked, omitting onError is missing_required_argument. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…ent pages Flutter had 0 of these while react has 128, android 112, angular 81, react-native 56 and ios 34. This closes the UI Kit half. Format follows the reference PRs (cometchat#446, cometchat#466, cometchat#471, cometchat#476): an Accordion straight after the frontmatter, a Field/Value table, and rows that let an agent decide whether the page is worth opening at all. Generated from the compiler-verified prop tables rather than hand-written, so every prop named here provably exists on the widget and the row cannot drift from the kit on the next release. 35 in-page anchors, all resolving. Two rows are Flutter-specific and are the reason a generic template would not have done: - Import carries the RIGHT BARREL per widget. Calling widgets resolve only from cometchat_calls_uikit.dart, so call-buttons, incoming-call, outgoing-call and call-logs also get an explicit Barrel row saying so. Importing a calling widget from the chat barrel is the most common Flutter compile failure and no other platform has this split. - Layout warns that list widgets fill their parent and need an Expanded or a sized box, because the failure is an unbounded-height throw at render rather than a build error. Plus the two traps found by building on the kit: message-list carries the addTemplate-not-templates rule, and message-composer carries the ccMessageSent requirement for messages sent outside it. Classification is by TYPE, not name, after three passes got it wrong: messagesRequestBuilder ends in Builder but is data, hideThreadView ends in View but is a bool toggle, headerView is a HeaderFooterBuilder typedef with neither Widget nor Function in its name, and onError is typed OnError? so only the on-plus-capital convention identifies it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

shagundeogharkar · 2026-08-17T13:51:27Z

What & why

Part of ENG-38204 (Angular skills — UI Kit + SDK). That ticket's blocking prerequisite is a scoped llms.txt-style index for Angular, because the skills pack is docs-maximal: it builds features from the official task guides and compares its output against them. Without a scoped index there is no way for an agent to discover which guides exist, so it silently falls back to component-wiring and loses the guide-first completeness check.

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index covering all 91 v5 pages as .md twins, in 13 sections. It mirrors the shape of ui-kit/react/llms-react-v7.mdx (currently on branch docs/react-v7-feature-guides, not yet on main).

No Angular SDK index is needed. The ticket asks for two indexes, but Angular consumes the same @cometchat/chat-sdk-javascript@4 as React, and the existing sdk/javascript/llms-javascript-v4.mdx is framework-agnostic — Angular inherits it unchanged.

Changes

New — `ui-kit/angular/llms-angular-v5.mdx`

Unlisted, NOT hidden. Deliberately omitted from docs.json navigation so it never appears in the human sidebar, but it still builds, serves its .md twin, and stays indexed. hidden: true was not used because Mintlify auto-applies noindex to hidden pages, which would drop this page from search and from the auto-generated global llms.txt — defeating the purpose. docs.json is untouched, so there are no navigation refs to break and no redirects required.
Scoped to v5 only. The 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces.
Angular-specific framing that the React index has no equivalent for: kebab-case selectors in templates (<cometchat-conversations>), @Input() rather than props, content-projection / TemplateRef rather than render props, and environment config in src/environments/environment.ts rather than .env.
Section spine: getting started · core & configuration · theming & customization · five component groups · Task guides (recipes) (17 entries) · framework recipes · migration.

Fixes — four content defects surfaced while building the index

Three pages shipped with no frontmatter at all, despite being present in docs.json navigation, so they render untitled on the live site. Added title/description per house style (cf. api-reference/chat-state-service.mdx), and removed the two leading H1s that would now duplicate the frontmatter title:

File	Was	Now
`api-reference/formatter-config-service.mdx`	no frontmatter	`title: "Formatter Config Service"`
`api-reference/rich-text-editor-service.mdx`	no frontmatter, leading `# RichTextEditorService API Reference`	`title: "Rich Text Editor Service"`
`guides/rich-text-formatting.mdx`	no frontmatter, leading `# Rich Text Formatting Guide`	`title: "Rich Text Formatting"`

overview.mdx — "AI Integration Quick Reference" listed incomplete peer deps.

	Value
Was	`@cometchat/chat-sdk-javascript`, `dompurify`
Now	`@cometchat/chat-sdk-javascript`, `@cometchat/cards-angular`, `dompurify`

Ground truth (verified against the shipped package)

The peer-dep fix was confirmed against the published package, not inferred:

$ npm view @cometchat/chat-uikit-angular@5.1.0 peerDependencies
{
"dompurify": "^3.0.0",
"@angular/core": ">=17.0.0 <22.0.0",
"@angular/common": ">=17.0.0 <22.0.0",
"@cometchat/cards-angular": "^1.0.0", ← undocumented
"@cometchat/chat-sdk-javascript": "^4.1.13",
"@cometchat/calls-sdk-javascript": "^5.0.3"
}

@cometchat/cards-angular was added between 5.0.3 and 5.1.0 (latest is 5.1.0; there is no v6 line). Anyone following the docs today gets an incomplete install.

Not fixed here — needs an owner decision

The same overview.mdx accordion states:

| Angular | v18, v19, v20, v21, v22 (v22 requires Node.js 24+) |

But the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0":

v22 is excluded — npm install @cometchat/chat-uikit-angular@^5 on an Angular 22 project hard-fails with ERESOLVE. The docs currently advertise a version where install is impossible.
v17 is supported but undocumented.

So either the docs or the kit's peer range is wrong. That is a support-policy call for the UI Kit owners, not a typo, so this PR leaves the line untouched and flags it instead. It also blocks the Angular core skill, which has to state a supported range.

Checklist

Branch name follows the naming convention (docs/angular-v5-llms-index)
docs.json untouched — no nav refs changed, no redirects needed
All 91 links generated from the actual ui-kit/angular file tree, with page titles read from each file's frontmatter
Peer-dep change verified against the published npm package
npx mintlify dev not yet run — before merge, please confirm the page builds (a "not in navigation" warning is expected and intended) and that /ui-kit/angular/llms-angular-v5.md resolves as raw Markdown. The design depends on that twin being fetchable.

Follow-ups (not in this PR)

Quick Reference accordions on the 43 components/cometchat-*.mdx pages. The index tells agents each .md twin carries input/output names, types and defaults. That holds for guides/ and integration.mdx, but the component pages have no accordion yet, so the promise is currently partial. The React equivalent added these across 56 files in the same branch; for Angular it is deliberately split out as a separate, mechanical PR.
React's own indexes are still unmerged (docs/react-v7-feature-guides, docs/js-sdk-llms-index). Merging this one puts Angular's index in production while React's stays on a preview deploy — worth deciding whether those two should land as well, since the React skills pack currently documents .mintlify.site preview URLs as its docs base.

@input

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index of all 91 v5 pages as .md twins, for AI coding agents. Mirrors the shape of ui-kit/react/llms-react-v7.mdx (branch docs/react-v7-feature-guides). - Unlisted, NOT hidden: omitted from docs.json navigation so it never shows in the human sidebar, but still built, served as a .md twin, and indexed. Using `hidden: true` would auto-apply noindex and drop it from search + the global llms.txt, which defeats the purpose. docs.json is deliberately untouched. - Scoped to v5 only; the 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces. - Angular-specific framing the React index has no equivalent for: kebab-case selectors, @input() rather than props, content-projection/TemplateRef rather than render props, and env config in src/environments/environment.ts. Also fixes four content defects surfaced while building the index: - api-reference/formatter-config-service.mdx, api-reference/ rich-text-editor-service.mdx and guides/rich-text-formatting.mdx shipped with NO frontmatter at all despite being in docs.json navigation, so they rendered untitled. Adds title/description per house style (see api-reference/chat-state-service.mdx) and drops the two leading H1s that would now duplicate the frontmatter title. - overview.mdx "AI Integration Quick Reference" listed peer deps as @cometchat/chat-sdk-javascript + dompurify, missing @cometchat/cards-angular@^1.0.0 which @cometchat/chat-uikit-angular@5.1.0 added. Verified against the published package. NOT fixed here, needs an owner decision: the same accordion claims Angular "v18, v19, v20, v21, v22" but the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0" — v22 is excluded (install hard-fails with ERESOLVE) and v17 is supported but undocumented. Either the docs or the peer range is wrong; that is a support-policy call, not a typo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mintlify · 2026-08-17T13:51:30Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cometchat	🟢 Ready	View Preview	Aug 17, 2026, 1:55 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

shagundeogharkar · 2026-08-19T13:16:21Z

Superseded by #475 — this branch is merged into docs/angular-v5-skills, which carries the same commits plus the remaining Angular docs work (AI Integration Quick Reference accordions across the 43 component pages). Keeping it as one PR gives a single Mintlify preview covering every change. Branch left in place; nothing lost.

Flutter was the only platform with none. On the skills-v5-temp base, react has 128 Quick References and 3 llms indexes, android 112/2, angular 81/1, react-native 56/2, ios 34/2 - and flutter 0 and 0. This closes the index half. Structure and conventions follow the reference PRs for the same feature: cometchat#446 (React v7), cometchat#466 (JS SDK), cometchat#471 (Angular v5), cometchat#476 (React Native). Unlisted rather than hidden, for the reason those PRs give: in Mintlify hidden auto-applies noindex, which would drop the page from search and from the auto global llms.txt - and the whole point is that an agent can discover it. Not registered in docs.json, same as every prior index. ui-kit/flutter/llms-flutter-v6.mdx 70 links, all 54 UI Kit pages sdk/flutter/llms-flutter-v5.mdx 58 links, all 52 SDK pages Both are 100 percent page coverage with zero dead links, verified by resolving every href against the tree. The Platform rules section is the part that carries real weight, and every claim in it was verified against cometchat_chat_uikit 6.1.0 rather than recalled: - TWO barrels with different surfaces. Chat widgets do not resolve from the calls barrel and vice versa, so a screen showing both imports both. This is the most common Flutter-specific compile failure. - Lists need a bounded box or layout throws at render, not at build. - Kit widgets paint their own surface; the app ThemeData does not reach inside. - Theming is ThemeExtension, and registering on only one of light/dark silently leaves the other on kit defaults. - v5's CometChatUIKit.getDataSource() is gone; v6 uses MessageTemplateUtils. - Custom message types need addTemplate, not templates - templates only registers the bubble and the message is filtered out before it can render, with no error. A hand-rolled MessagesRequestBuilder does not help because the list always overrides uid/guid/types/categories on it. - Messages sent with CometChat.send*Message must emit ccMessageSent or a mounted list never shows them. - SDK: onSuccess AND onError are both required - compile-checked, omitting onError is missing_required_argument. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…ent pages Flutter had 0 of these while react has 128, android 112, angular 81, react-native 56 and ios 34. This closes the UI Kit half. Format follows the reference PRs (cometchat#446, cometchat#466, cometchat#471, cometchat#476): an Accordion straight after the frontmatter, a Field/Value table, and rows that let an agent decide whether the page is worth opening at all. Generated from the compiler-verified prop tables rather than hand-written, so every prop named here provably exists on the widget and the row cannot drift from the kit on the next release. 35 in-page anchors, all resolving. Two rows are Flutter-specific and are the reason a generic template would not have done: - Import carries the RIGHT BARREL per widget. Calling widgets resolve only from cometchat_calls_uikit.dart, so call-buttons, incoming-call, outgoing-call and call-logs also get an explicit Barrel row saying so. Importing a calling widget from the chat barrel is the most common Flutter compile failure and no other platform has this split. - Layout warns that list widgets fill their parent and need an Expanded or a sized box, because the failure is an unbounded-height throw at render rather than a build error. Plus the two traps found by building on the kit: message-list carries the addTemplate-not-templates rule, and message-composer carries the ccMessageSent requirement for messages sent outside it. Classification is by TYPE, not name, after three passes got it wrong: messagesRequestBuilder ends in Builder but is data, hideThreadView ends in View but is a bool toggle, headerView is a HeaderFooterBuilder typedef with neither Widget nor Function in its name, and onError is typed OnError? so only the on-plus-capital convention identifies it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

shagundeogharkar · 2026-08-17T13:51:27Z

What & why

Part of ENG-38204 (Angular skills — UI Kit + SDK). That ticket's blocking prerequisite is a scoped llms.txt-style index for Angular, because the skills pack is docs-maximal: it builds features from the official task guides and compares its output against them. Without a scoped index there is no way for an agent to discover which guides exist, so it silently falls back to component-wiring and loses the guide-first completeness check.

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index covering all 91 v5 pages as .md twins, in 13 sections. It mirrors the shape of ui-kit/react/llms-react-v7.mdx (currently on branch docs/react-v7-feature-guides, not yet on main).

No Angular SDK index is needed. The ticket asks for two indexes, but Angular consumes the same @cometchat/chat-sdk-javascript@4 as React, and the existing sdk/javascript/llms-javascript-v4.mdx is framework-agnostic — Angular inherits it unchanged.

Changes

New — `ui-kit/angular/llms-angular-v5.mdx`

Unlisted, NOT hidden. Deliberately omitted from docs.json navigation so it never appears in the human sidebar, but it still builds, serves its .md twin, and stays indexed. hidden: true was not used because Mintlify auto-applies noindex to hidden pages, which would drop this page from search and from the auto-generated global llms.txt — defeating the purpose. docs.json is untouched, so there are no navigation refs to break and no redirects required.
Scoped to v5 only. The 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces.
Angular-specific framing that the React index has no equivalent for: kebab-case selectors in templates (<cometchat-conversations>), @Input() rather than props, content-projection / TemplateRef rather than render props, and environment config in src/environments/environment.ts rather than .env.
Section spine: getting started · core & configuration · theming & customization · five component groups · Task guides (recipes) (17 entries) · framework recipes · migration.

Fixes — four content defects surfaced while building the index

Three pages shipped with no frontmatter at all, despite being present in docs.json navigation, so they render untitled on the live site. Added title/description per house style (cf. api-reference/chat-state-service.mdx), and removed the two leading H1s that would now duplicate the frontmatter title:

File	Was	Now
`api-reference/formatter-config-service.mdx`	no frontmatter	`title: "Formatter Config Service"`
`api-reference/rich-text-editor-service.mdx`	no frontmatter, leading `# RichTextEditorService API Reference`	`title: "Rich Text Editor Service"`
`guides/rich-text-formatting.mdx`	no frontmatter, leading `# Rich Text Formatting Guide`	`title: "Rich Text Formatting"`

overview.mdx — "AI Integration Quick Reference" listed incomplete peer deps.

	Value
Was	`@cometchat/chat-sdk-javascript`, `dompurify`
Now	`@cometchat/chat-sdk-javascript`, `@cometchat/cards-angular`, `dompurify`

Ground truth (verified against the shipped package)

The peer-dep fix was confirmed against the published package, not inferred:

$ npm view @cometchat/chat-uikit-angular@5.1.0 peerDependencies
{
"dompurify": "^3.0.0",
"@angular/core": ">=17.0.0 <22.0.0",
"@angular/common": ">=17.0.0 <22.0.0",
"@cometchat/cards-angular": "^1.0.0", ← undocumented
"@cometchat/chat-sdk-javascript": "^4.1.13",
"@cometchat/calls-sdk-javascript": "^5.0.3"
}

@cometchat/cards-angular was added between 5.0.3 and 5.1.0 (latest is 5.1.0; there is no v6 line). Anyone following the docs today gets an incomplete install.

Not fixed here — needs an owner decision

The same overview.mdx accordion states:

| Angular | v18, v19, v20, v21, v22 (v22 requires Node.js 24+) |

But the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0":

v22 is excluded — npm install @cometchat/chat-uikit-angular@^5 on an Angular 22 project hard-fails with ERESOLVE. The docs currently advertise a version where install is impossible.
v17 is supported but undocumented.

So either the docs or the kit's peer range is wrong. That is a support-policy call for the UI Kit owners, not a typo, so this PR leaves the line untouched and flags it instead. It also blocks the Angular core skill, which has to state a supported range.

Checklist

Branch name follows the naming convention (docs/angular-v5-llms-index)
docs.json untouched — no nav refs changed, no redirects needed
All 91 links generated from the actual ui-kit/angular file tree, with page titles read from each file's frontmatter
Peer-dep change verified against the published npm package
npx mintlify dev not yet run — before merge, please confirm the page builds (a "not in navigation" warning is expected and intended) and that /ui-kit/angular/llms-angular-v5.md resolves as raw Markdown. The design depends on that twin being fetchable.

Follow-ups (not in this PR)

Quick Reference accordions on the 43 components/cometchat-*.mdx pages. The index tells agents each .md twin carries input/output names, types and defaults. That holds for guides/ and integration.mdx, but the component pages have no accordion yet, so the promise is currently partial. The React equivalent added these across 56 files in the same branch; for Angular it is deliberately split out as a separate, mechanical PR.
React's own indexes are still unmerged (docs/react-v7-feature-guides, docs/js-sdk-llms-index). Merging this one puts Angular's index in production while React's stays on a preview deploy — worth deciding whether those two should land as well, since the React skills pack currently documents .mintlify.site preview URLs as its docs base.

@input

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index of all 91 v5 pages as .md twins, for AI coding agents. Mirrors the shape of ui-kit/react/llms-react-v7.mdx (branch docs/react-v7-feature-guides). - Unlisted, NOT hidden: omitted from docs.json navigation so it never shows in the human sidebar, but still built, served as a .md twin, and indexed. Using `hidden: true` would auto-apply noindex and drop it from search + the global llms.txt, which defeats the purpose. docs.json is deliberately untouched. - Scoped to v5 only; the 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces. - Angular-specific framing the React index has no equivalent for: kebab-case selectors, @input() rather than props, content-projection/TemplateRef rather than render props, and env config in src/environments/environment.ts. Also fixes four content defects surfaced while building the index: - api-reference/formatter-config-service.mdx, api-reference/ rich-text-editor-service.mdx and guides/rich-text-formatting.mdx shipped with NO frontmatter at all despite being in docs.json navigation, so they rendered untitled. Adds title/description per house style (see api-reference/chat-state-service.mdx) and drops the two leading H1s that would now duplicate the frontmatter title. - overview.mdx "AI Integration Quick Reference" listed peer deps as @cometchat/chat-sdk-javascript + dompurify, missing @cometchat/cards-angular@^1.0.0 which @cometchat/chat-uikit-angular@5.1.0 added. Verified against the published package. NOT fixed here, needs an owner decision: the same accordion claims Angular "v18, v19, v20, v21, v22" but the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0" — v22 is excluded (install hard-fails with ERESOLVE) and v17 is supported but undocumented. Either the docs or the peer range is wrong; that is a support-policy call, not a typo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mintlify · 2026-08-17T13:51:30Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cometchat	🟢 Ready	View Preview	Aug 17, 2026, 1:55 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

shagundeogharkar · 2026-08-19T13:16:21Z

Superseded by #475 — this branch is merged into docs/angular-v5-skills, which carries the same commits plus the remaining Angular docs work (AI Integration Quick Reference accordions across the 43 component pages). Keeping it as one PR gives a single Mintlify preview covering every change. Branch left in place; nothing lost.

Flutter was the only platform with none. On the skills-v5-temp base, react has 128 Quick References and 3 llms indexes, android 112/2, angular 81/1, react-native 56/2, ios 34/2 - and flutter 0 and 0. This closes the index half. Structure and conventions follow the reference PRs for the same feature: cometchat#446 (React v7), cometchat#466 (JS SDK), cometchat#471 (Angular v5), cometchat#476 (React Native). Unlisted rather than hidden, for the reason those PRs give: in Mintlify hidden auto-applies noindex, which would drop the page from search and from the auto global llms.txt - and the whole point is that an agent can discover it. Not registered in docs.json, same as every prior index. ui-kit/flutter/llms-flutter-v6.mdx 70 links, all 54 UI Kit pages sdk/flutter/llms-flutter-v5.mdx 58 links, all 52 SDK pages Both are 100 percent page coverage with zero dead links, verified by resolving every href against the tree. The Platform rules section is the part that carries real weight, and every claim in it was verified against cometchat_chat_uikit 6.1.0 rather than recalled: - TWO barrels with different surfaces. Chat widgets do not resolve from the calls barrel and vice versa, so a screen showing both imports both. This is the most common Flutter-specific compile failure. - Lists need a bounded box or layout throws at render, not at build. - Kit widgets paint their own surface; the app ThemeData does not reach inside. - Theming is ThemeExtension, and registering on only one of light/dark silently leaves the other on kit defaults. - v5's CometChatUIKit.getDataSource() is gone; v6 uses MessageTemplateUtils. - Custom message types need addTemplate, not templates - templates only registers the bubble and the message is filtered out before it can render, with no error. A hand-rolled MessagesRequestBuilder does not help because the list always overrides uid/guid/types/categories on it. - Messages sent with CometChat.send*Message must emit ccMessageSent or a mounted list never shows them. - SDK: onSuccess AND onError are both required - compile-checked, omitting onError is missing_required_argument. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…ent pages Flutter had 0 of these while react has 128, android 112, angular 81, react-native 56 and ios 34. This closes the UI Kit half. Format follows the reference PRs (cometchat#446, cometchat#466, cometchat#471, cometchat#476): an Accordion straight after the frontmatter, a Field/Value table, and rows that let an agent decide whether the page is worth opening at all. Generated from the compiler-verified prop tables rather than hand-written, so every prop named here provably exists on the widget and the row cannot drift from the kit on the next release. 35 in-page anchors, all resolving. Two rows are Flutter-specific and are the reason a generic template would not have done: - Import carries the RIGHT BARREL per widget. Calling widgets resolve only from cometchat_calls_uikit.dart, so call-buttons, incoming-call, outgoing-call and call-logs also get an explicit Barrel row saying so. Importing a calling widget from the chat barrel is the most common Flutter compile failure and no other platform has this split. - Layout warns that list widgets fill their parent and need an Expanded or a sized box, because the failure is an unbounded-height throw at render rather than a build error. Plus the two traps found by building on the kit: message-list carries the addTemplate-not-templates rule, and message-composer carries the ccMessageSent requirement for messages sent outside it. Classification is by TYPE, not name, after three passes got it wrong: messagesRequestBuilder ends in Builder but is data, hideThreadView ends in View but is a bool toggle, headerView is a HeaderFooterBuilder typedef with neither Widget nor Function in its name, and onError is typed OnError? so only the on-plus-capital convention identifies it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

shagundeogharkar · 2026-08-17T13:51:27Z

What & why

Part of ENG-38204 (Angular skills — UI Kit + SDK). That ticket's blocking prerequisite is a scoped llms.txt-style index for Angular, because the skills pack is docs-maximal: it builds features from the official task guides and compares its output against them. Without a scoped index there is no way for an agent to discover which guides exist, so it silently falls back to component-wiring and loses the guide-first completeness check.

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index covering all 91 v5 pages as .md twins, in 13 sections. It mirrors the shape of ui-kit/react/llms-react-v7.mdx (currently on branch docs/react-v7-feature-guides, not yet on main).

No Angular SDK index is needed. The ticket asks for two indexes, but Angular consumes the same @cometchat/chat-sdk-javascript@4 as React, and the existing sdk/javascript/llms-javascript-v4.mdx is framework-agnostic — Angular inherits it unchanged.

Changes

New — `ui-kit/angular/llms-angular-v5.mdx`

Unlisted, NOT hidden. Deliberately omitted from docs.json navigation so it never appears in the human sidebar, but it still builds, serves its .md twin, and stays indexed. hidden: true was not used because Mintlify auto-applies noindex to hidden pages, which would drop this page from search and from the auto-generated global llms.txt — defeating the purpose. docs.json is untouched, so there are no navigation refs to break and no redirects required.
Scoped to v5 only. The 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces.
Angular-specific framing that the React index has no equivalent for: kebab-case selectors in templates (<cometchat-conversations>), @Input() rather than props, content-projection / TemplateRef rather than render props, and environment config in src/environments/environment.ts rather than .env.
Section spine: getting started · core & configuration · theming & customization · five component groups · Task guides (recipes) (17 entries) · framework recipes · migration.

Fixes — four content defects surfaced while building the index

Three pages shipped with no frontmatter at all, despite being present in docs.json navigation, so they render untitled on the live site. Added title/description per house style (cf. api-reference/chat-state-service.mdx), and removed the two leading H1s that would now duplicate the frontmatter title:

File	Was	Now
`api-reference/formatter-config-service.mdx`	no frontmatter	`title: "Formatter Config Service"`
`api-reference/rich-text-editor-service.mdx`	no frontmatter, leading `# RichTextEditorService API Reference`	`title: "Rich Text Editor Service"`
`guides/rich-text-formatting.mdx`	no frontmatter, leading `# Rich Text Formatting Guide`	`title: "Rich Text Formatting"`

overview.mdx — "AI Integration Quick Reference" listed incomplete peer deps.

	Value
Was	`@cometchat/chat-sdk-javascript`, `dompurify`
Now	`@cometchat/chat-sdk-javascript`, `@cometchat/cards-angular`, `dompurify`

Ground truth (verified against the shipped package)

The peer-dep fix was confirmed against the published package, not inferred:

$ npm view @cometchat/chat-uikit-angular@5.1.0 peerDependencies
{
"dompurify": "^3.0.0",
"@angular/core": ">=17.0.0 <22.0.0",
"@angular/common": ">=17.0.0 <22.0.0",
"@cometchat/cards-angular": "^1.0.0", ← undocumented
"@cometchat/chat-sdk-javascript": "^4.1.13",
"@cometchat/calls-sdk-javascript": "^5.0.3"
}

@cometchat/cards-angular was added between 5.0.3 and 5.1.0 (latest is 5.1.0; there is no v6 line). Anyone following the docs today gets an incomplete install.

Not fixed here — needs an owner decision

The same overview.mdx accordion states:

| Angular | v18, v19, v20, v21, v22 (v22 requires Node.js 24+) |

But the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0":

v22 is excluded — npm install @cometchat/chat-uikit-angular@^5 on an Angular 22 project hard-fails with ERESOLVE. The docs currently advertise a version where install is impossible.
v17 is supported but undocumented.

So either the docs or the kit's peer range is wrong. That is a support-policy call for the UI Kit owners, not a typo, so this PR leaves the line untouched and flags it instead. It also blocks the Angular core skill, which has to state a supported range.

Checklist

Branch name follows the naming convention (docs/angular-v5-llms-index)
docs.json untouched — no nav refs changed, no redirects needed
All 91 links generated from the actual ui-kit/angular file tree, with page titles read from each file's frontmatter
Peer-dep change verified against the published npm package
npx mintlify dev not yet run — before merge, please confirm the page builds (a "not in navigation" warning is expected and intended) and that /ui-kit/angular/llms-angular-v5.md resolves as raw Markdown. The design depends on that twin being fetchable.

Follow-ups (not in this PR)

Quick Reference accordions on the 43 components/cometchat-*.mdx pages. The index tells agents each .md twin carries input/output names, types and defaults. That holds for guides/ and integration.mdx, but the component pages have no accordion yet, so the promise is currently partial. The React equivalent added these across 56 files in the same branch; for Angular it is deliberately split out as a separate, mechanical PR.
React's own indexes are still unmerged (docs/react-v7-feature-guides, docs/js-sdk-llms-index). Merging this one puts Angular's index in production while React's stays on a preview deploy — worth deciding whether those two should land as well, since the React skills pack currently documents .mintlify.site preview URLs as its docs base.

@input

Adds ui-kit/angular/llms-angular-v5.mdx — a machine-readable, Angular-v5-scoped routing index of all 91 v5 pages as .md twins, for AI coding agents. Mirrors the shape of ui-kit/react/llms-react-v7.mdx (branch docs/react-v7-feature-guides). - Unlisted, NOT hidden: omitted from docs.json navigation so it never shows in the human sidebar, but still built, served as a .md twin, and indexed. Using `hidden: true` would auto-apply noindex and drop it from search + the global llms.txt, which defeats the purpose. docs.json is deliberately untouched. - Scoped to v5 only; the 2.0/, 3.0/ and v4/ trees are excluded so agents are never routed at dead API surfaces. - Angular-specific framing the React index has no equivalent for: kebab-case selectors, @input() rather than props, content-projection/TemplateRef rather than render props, and env config in src/environments/environment.ts. Also fixes four content defects surfaced while building the index: - api-reference/formatter-config-service.mdx, api-reference/ rich-text-editor-service.mdx and guides/rich-text-formatting.mdx shipped with NO frontmatter at all despite being in docs.json navigation, so they rendered untitled. Adds title/description per house style (see api-reference/chat-state-service.mdx) and drops the two leading H1s that would now duplicate the frontmatter title. - overview.mdx "AI Integration Quick Reference" listed peer deps as @cometchat/chat-sdk-javascript + dompurify, missing @cometchat/cards-angular@^1.0.0 which @cometchat/chat-uikit-angular@5.1.0 added. Verified against the published package. NOT fixed here, needs an owner decision: the same accordion claims Angular "v18, v19, v20, v21, v22" but the published peer range at 5.1.0 is @angular/core ">=17.0.0 <22.0.0" — v22 is excluded (install hard-fails with ERESOLVE) and v17 is supported but undocumented. Either the docs or the peer range is wrong; that is a support-policy call, not a typo. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

mintlify · 2026-08-17T13:51:30Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
cometchat	🟢 Ready	View Preview	Aug 17, 2026, 1:55 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

shagundeogharkar · 2026-08-19T13:16:21Z

Superseded by #475 — this branch is merged into docs/angular-v5-skills, which carries the same commits plus the remaining Angular docs work (AI Integration Quick Reference accordions across the 43 component pages). Keeping it as one PR gives a single Mintlify preview covering every change. Branch left in place; nothing lost.

Flutter was the only platform with none. On the skills-v5-temp base, react has 128 Quick References and 3 llms indexes, android 112/2, angular 81/1, react-native 56/2, ios 34/2 - and flutter 0 and 0. This closes the index half. Structure and conventions follow the reference PRs for the same feature: cometchat#446 (React v7), cometchat#466 (JS SDK), cometchat#471 (Angular v5), cometchat#476 (React Native). Unlisted rather than hidden, for the reason those PRs give: in Mintlify hidden auto-applies noindex, which would drop the page from search and from the auto global llms.txt - and the whole point is that an agent can discover it. Not registered in docs.json, same as every prior index. ui-kit/flutter/llms-flutter-v6.mdx 70 links, all 54 UI Kit pages sdk/flutter/llms-flutter-v5.mdx 58 links, all 52 SDK pages Both are 100 percent page coverage with zero dead links, verified by resolving every href against the tree. The Platform rules section is the part that carries real weight, and every claim in it was verified against cometchat_chat_uikit 6.1.0 rather than recalled: - TWO barrels with different surfaces. Chat widgets do not resolve from the calls barrel and vice versa, so a screen showing both imports both. This is the most common Flutter-specific compile failure. - Lists need a bounded box or layout throws at render, not at build. - Kit widgets paint their own surface; the app ThemeData does not reach inside. - Theming is ThemeExtension, and registering on only one of light/dark silently leaves the other on kit defaults. - v5's CometChatUIKit.getDataSource() is gone; v6 uses MessageTemplateUtils. - Custom message types need addTemplate, not templates - templates only registers the bubble and the message is filtered out before it can render, with no error. A hand-rolled MessagesRequestBuilder does not help because the list always overrides uid/guid/types/categories on it. - Messages sent with CometChat.send*Message must emit ccMessageSent or a mounted list never shows them. - SDK: onSuccess AND onError are both required - compile-checked, omitting onError is missing_required_argument. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

…ent pages Flutter had 0 of these while react has 128, android 112, angular 81, react-native 56 and ios 34. This closes the UI Kit half. Format follows the reference PRs (cometchat#446, cometchat#466, cometchat#471, cometchat#476): an Accordion straight after the frontmatter, a Field/Value table, and rows that let an agent decide whether the page is worth opening at all. Generated from the compiler-verified prop tables rather than hand-written, so every prop named here provably exists on the widget and the row cannot drift from the kit on the next release. 35 in-page anchors, all resolving. Two rows are Flutter-specific and are the reason a generic template would not have done: - Import carries the RIGHT BARREL per widget. Calling widgets resolve only from cometchat_calls_uikit.dart, so call-buttons, incoming-call, outgoing-call and call-logs also get an explicit Barrel row saying so. Importing a calling widget from the chat barrel is the most common Flutter compile failure and no other platform has this split. - Layout warns that list widgets fill their parent and need an Expanded or a sized box, because the failure is an unbounded-height throw at render rather than a build error. Plus the two traps found by building on the kit: message-list carries the addTemplate-not-templates rule, and message-composer carries the ccMessageSent requirement for messages sent outside it. Classification is by TYPE, not name, after three passes got it wrong: messagesRequestBuilder ends in Builder but is data, hideThreadView ends in View but is a bool toggle, headerView is a HeaderFooterBuilder typedef with neither Widget nor Function in its name, and onError is typed OnError? so only the on-plus-capital convention identifies it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

shagundeogharkar requested a review from raj-dubey1 as a code owner August 17, 2026 13:51

mintlifyBotdeployed to staging August 17, 2026 13:55 View deployment

suraj-chauhan-cometchat mentioned this pull request Aug 19, 2026
docs(react-native): scoped LLM indexes for UI Kit v5 + SDK v4 (ENG-38205) #474
Closed

shagundeogharkar mentioned this pull request Aug 19, 2026
docs(ui-kit/angular): Angular v5 skills docs — LLM index + AI Integration Quick References (ENG-38204) #475
Merged
6 tasks

shagundeogharkar closed this Aug 19, 2026

suraj-chauhan-cometchat mentioned this pull request Aug 20, 2026
docs(react-native): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes (ENG-38205) #476
Merged

anshuman-cometchat mentioned this pull request Aug 25, 2026
docs(flutter): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes #483
Merged

shagundeogharkar requested a review from raj-dubey1 as a code owner August 17, 2026 13:51

mintlifyBotdeployed to staging August 17, 2026 13:55 View deployment

suraj-chauhan-cometchat mentioned this pull request Aug 19, 2026
docs(react-native): scoped LLM indexes for UI Kit v5 + SDK v4 (ENG-38205) #474
Closed

shagundeogharkar mentioned this pull request Aug 19, 2026
docs(ui-kit/angular): Angular v5 skills docs — LLM index + AI Integration Quick References (ENG-38204) #475
Merged
6 tasks

shagundeogharkar closed this Aug 19, 2026

suraj-chauhan-cometchat mentioned this pull request Aug 20, 2026
docs(react-native): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes (ENG-38205) #476
Merged

anshuman-cometchat mentioned this pull request Aug 25, 2026
docs(flutter): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes #483
Merged

shagundeogharkar requested a review from raj-dubey1 as a code owner August 17, 2026 13:51

mintlifyBotdeployed to staging August 17, 2026 13:55 View deployment

suraj-chauhan-cometchat mentioned this pull request Aug 19, 2026
docs(react-native): scoped LLM indexes for UI Kit v5 + SDK v4 (ENG-38205) #474
Closed

shagundeogharkar mentioned this pull request Aug 19, 2026
docs(ui-kit/angular): Angular v5 skills docs — LLM index + AI Integration Quick References (ENG-38204) #475
Merged
6 tasks

shagundeogharkar closed this Aug 19, 2026

suraj-chauhan-cometchat mentioned this pull request Aug 20, 2026
docs(react-native): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes (ENG-38205) #476
Merged

anshuman-cometchat mentioned this pull request Aug 25, 2026
docs(flutter): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes #483
Merged

shagundeogharkar requested a review from raj-dubey1 as a code owner August 17, 2026 13:51

mintlifyBotdeployed to staging August 17, 2026 13:55 View deployment

suraj-chauhan-cometchat mentioned this pull request Aug 19, 2026
docs(react-native): scoped LLM indexes for UI Kit v5 + SDK v4 (ENG-38205) #474
Closed

shagundeogharkar mentioned this pull request Aug 19, 2026
docs(ui-kit/angular): Angular v5 skills docs — LLM index + AI Integration Quick References (ENG-38204) #475
Merged
6 tasks

shagundeogharkar closed this Aug 19, 2026

suraj-chauhan-cometchat mentioned this pull request Aug 20, 2026
docs(react-native): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes (ENG-38205) #476
Merged

anshuman-cometchat mentioned this pull request Aug 25, 2026
docs(flutter): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes #483
Merged

shagundeogharkar requested a review from raj-dubey1 as a code owner August 17, 2026 13:51

mintlifyBotdeployed to staging August 17, 2026 13:55 View deployment

suraj-chauhan-cometchat mentioned this pull request Aug 19, 2026
docs(react-native): scoped LLM indexes for UI Kit v5 + SDK v4 (ENG-38205) #474
Closed

shagundeogharkar mentioned this pull request Aug 19, 2026
docs(ui-kit/angular): Angular v5 skills docs — LLM index + AI Integration Quick References (ENG-38204) #475
Merged
6 tasks

shagundeogharkar closed this Aug 19, 2026

suraj-chauhan-cometchat mentioned this pull request Aug 20, 2026
docs(react-native): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes (ENG-38205) #476
Merged

anshuman-cometchat mentioned this pull request Aug 25, 2026
docs(flutter): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes #483
Merged

shagundeogharkar requested a review from raj-dubey1 as a code owner August 17, 2026 13:51

mintlifyBotdeployed to staging August 17, 2026 13:55 View deployment

suraj-chauhan-cometchat mentioned this pull request Aug 19, 2026
docs(react-native): scoped LLM indexes for UI Kit v5 + SDK v4 (ENG-38205) #474
Closed

shagundeogharkar mentioned this pull request Aug 19, 2026
docs(ui-kit/angular): Angular v5 skills docs — LLM index + AI Integration Quick References (ENG-38204) #475
Merged
6 tasks

shagundeogharkar closed this Aug 19, 2026

suraj-chauhan-cometchat mentioned this pull request Aug 20, 2026
docs(react-native): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes (ENG-38205) #476
Merged

anshuman-cometchat mentioned this pull request Aug 25, 2026
docs(flutter): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes #483
Merged

shagundeogharkar requested a review from raj-dubey1 as a code owner August 17, 2026 13:51

mintlifyBotdeployed to staging August 17, 2026 13:55 View deployment

suraj-chauhan-cometchat mentioned this pull request Aug 19, 2026
docs(react-native): scoped LLM indexes for UI Kit v5 + SDK v4 (ENG-38205) #474
Closed

shagundeogharkar mentioned this pull request Aug 19, 2026
docs(ui-kit/angular): Angular v5 skills docs — LLM index + AI Integration Quick References (ENG-38204) #475
Merged
6 tasks

shagundeogharkar closed this Aug 19, 2026

suraj-chauhan-cometchat mentioned this pull request Aug 20, 2026
docs(react-native): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes (ENG-38205) #476
Merged

anshuman-cometchat mentioned this pull request Aug 25, 2026
docs(flutter): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes #483
Merged

shagundeogharkar requested a review from raj-dubey1 as a code owner August 17, 2026 13:51

mintlifyBotdeployed to staging August 17, 2026 13:55 View deployment

suraj-chauhan-cometchat mentioned this pull request Aug 19, 2026
docs(react-native): scoped LLM indexes for UI Kit v5 + SDK v4 (ENG-38205) #474
Closed

shagundeogharkar mentioned this pull request Aug 19, 2026
docs(ui-kit/angular): Angular v5 skills docs — LLM index + AI Integration Quick References (ENG-38204) #475
Merged
6 tasks

shagundeogharkar closed this Aug 19, 2026

suraj-chauhan-cometchat mentioned this pull request Aug 20, 2026
docs(react-native): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes (ENG-38205) #476
Merged

anshuman-cometchat mentioned this pull request Aug 25, 2026
docs(flutter): AI-agent docs layer — scoped LLM indexes, Quick References, and kit-vs-docs fixes #483
Merged

Uh oh!

Conversation

shagundeogharkar commented Aug 17, 2026

What & why

Changes

New — ui-kit/angular/llms-angular-v5.mdx

Fixes — four content defects surfaced while building the index

Ground truth (verified against the shipped package)

Not fixed here — needs an owner decision

Checklist

Follow-ups (not in this PR)

Uh oh!

mintlifyBot commented Aug 17, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

shagundeogharkar commented Aug 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

shagundeogharkar commented Aug 17, 2026

What & why

Changes

New — ui-kit/angular/llms-angular-v5.mdx

Fixes — four content defects surfaced while building the index

Ground truth (verified against the shipped package)

Not fixed here — needs an owner decision

Checklist

Follow-ups (not in this PR)

Uh oh!

mintlifyBot commented Aug 17, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

shagundeogharkar commented Aug 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

shagundeogharkar commented Aug 17, 2026

What & why

Changes

New — ui-kit/angular/llms-angular-v5.mdx

Fixes — four content defects surfaced while building the index

Ground truth (verified against the shipped package)

Not fixed here — needs an owner decision

Checklist

Follow-ups (not in this PR)

Uh oh!

mintlifyBot commented Aug 17, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

shagundeogharkar commented Aug 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

shagundeogharkar commented Aug 17, 2026

What & why

Changes

New — ui-kit/angular/llms-angular-v5.mdx

Fixes — four content defects surfaced while building the index

Ground truth (verified against the shipped package)

New — `ui-kit/angular/llms-angular-v5.mdx`

mintlifyBot commented Aug 17, 2026•
edited
Loading

New — `ui-kit/angular/llms-angular-v5.mdx`

mintlifyBot commented Aug 17, 2026•
edited
Loading

New — `ui-kit/angular/llms-angular-v5.mdx`

mintlifyBot commented Aug 17, 2026•
edited
Loading

New — `ui-kit/angular/llms-angular-v5.mdx`

mintlifyBot commented Aug 17, 2026•
edited
Loading

New — `ui-kit/angular/llms-angular-v5.mdx`

mintlifyBot commented Aug 17, 2026•
edited
Loading