docs: dimension links render inline in Workbooks - #11452
Conversation
…d the link format object form
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Claude finished @igorlukanin's task in 1m 58s —— View job Docs review: accurate against the code — 1 broken anchor, 1 stale sibling pageFull review (2 inline comments)
Verified against the code
The Findings
Smaller notes
No security, performance, or test concerns — docs-only change. |
… the dimensions concept page
|
Claude finished @igorlukanin's task in 1m 20s —— View job Docs review: both prior findings fixed; new content verified against the code — 0 blocking, 3 nitsFull review
Prior findings — both addressed
Agreed on skipping the version note — inline rendering ships with Workbooks, not a Core runtime version, so a Verified against the code
Anchor check — all resolve: The Nits (non-blocking)
Style matches • branch |
…ry in the concept example
|
Took nits 1 and 2 in |
|
Claude finished @igorlukanin's task in 1m 13s —— View job Docs review (
|
| Nit | Status |
|---|---|
| Empty-URL sentence read as general | ✅ reference/…/dimensions.mdx:474 now says "Rows whose primary link URL resolves to an empty value render the cell as plain text" — no longer collides with the concept page's Null values bullet, which is about the menu |
Concept-page example omitted primary |
✅ docs/…/dimensions.mdx:436 marks the search link primary: true, with a comment explaining what it does. The two pages' examples are now symmetric |
Verified against the code
| Claim | Source | Status |
|---|---|---|
primary: true accepted on a link |
CubeValidator.ts:321 — primary: Joi.boolean().strict() |
✅ |
| At most one primary per dimension | CubeValidator.ts:337-339 — Only one link can be marked as primary |
✅ |
format: { type: link, label: … } |
CubeValidator.ts:116-123 formatAlternatives (type optional, label required) |
✅ |
Object form belongs under string dimensions |
formatSchema is the otherwise branch; time/number have their own schemas |
✅ correctly placed |
Anchors — all resolve: #links (table.mdx:83), #cell-menu (table.mdx:158), #behavior (concept :504), #links (concept :382), #format (reference :262), [ref-workbooks] defined at reference :1362. No inbound links to the old #display-tab-… anchor anywhere in docs-mintlify/.
The http/https/mailto restriction and the Style-tab picker behavior are Workbooks frontend, not present in this repo — taken on trust, as before.
Nit (non-blocking) — one new
Duplicate example. The new format object-form code block (reference/…/dimensions.mdx:277-284) repeats the pre-existing crm_link dimension in the CodeGroup 45 lines below (:327-332, mirrored in the JS tab at :363) — same name, same SQL, same label, only the key order differs. The prose is the real addition here; the block is redundant against docs-mintlify/CLAUDE.md's "say it once". Inline suggestion posted keeping the sentence and pointing at the existing example. Fix this →
Anchor churn from ## Display tab → ## Style tab was already flagged and accepted — internally clean, only external bookmarks land at the top of the page.
Both earlier threads are resolved by the author; nothing to re-affirm. Style matches docs-mintlify/CLAUDE.md: surgical edits to existing pages, screenshot placeholders in the established MDX-comment form, no "Cube Cloud" in newly written prose. Docs-only change — no security, performance, or test concerns.
• branch igor/cub-2253-render-values-as-links-docs •
|
Claude finished @igorlukanin's task in 1m 9s —— View job Docs review (
|
| Claim | Source | Status |
|---|---|---|
primary: true accepted on a link |
CubeValidator.ts:321 — primary: Joi.boolean().strict() |
✅ |
| At most one primary per dimension | CubeValidator.ts:337-339 — Only one link can be marked as primary |
✅ |
format: { type: link, label: … } |
CubeValidator.ts:116-123 formatAlternatives (type optional, label required) |
✅ |
Object form belongs under string dimensions |
formatSchema is the otherwise branch; time/number have their own schemas |
✅ correctly placed |
Anchors and link references — all resolve
| Reference | Target | Status |
|---|---|---|
/reference/data-modeling/dimensions#format (table.mdx:93) |
### \format`at reference:262` |
✅ |
/docs/data-modeling/dimensions#links (table.mdx:90) |
## Links at concept :382 |
✅ |
#cell-menu (table.mdx:92) |
## Cell menu at table.mdx:158 |
✅ |
#behavior (concept :411, :520) |
### Behavior at concept :504 |
✅ |
[ref-workbooks] (3 new uses) |
defined at reference :1353 |
✅ |
/docs/explore-analyze/charts/chart-types/table#links (concept :521) |
### Links at table.mdx:83 |
✅ |
No inbound links to the old #display-tab-… anchor anywhere in docs-mintlify/ (grepped for display-tab — zero matches), so the ## Display tab → ## Style tab rename is internally clean. Already flagged and accepted: external bookmarks land at the top of the page.
The http/https/mailto restriction and the Style-tab picker behavior are Workbooks frontend, not present in this repo — taken on trust, as in the earlier rounds.
Nit (trivial, non-blocking)
The prose writes the object form as format: { type: link, label: … } (:274) while the example it points at spells the keys in the other order — label first, then type (:322-323, mirrored in JS at :358-359). Key order is irrelevant to YAML, but a reader jumping from the sentence to the example matches on shape. Swapping the two lines in the example would make the pair read as the same thing. Not worth a commit on its own.
Threads
All three of my earlier threads are already resolved and outdated — nothing to resolve or re-affirm. No new inline comments; the single remaining nit is too small to warrant one.
Docs-only change — no security, performance, or test concerns. Style matches docs-mintlify/CLAUDE.md: surgical edits to existing pages, no padding, screenshot placeholders in the page's established MDX-comment form, no "Cube Cloud" in newly written prose.
|
Claude finished @igorlukanin's task in 44s —— View job Docs review (
|
| Claim | Source | Status |
|---|---|---|
primary: true accepted on a link |
CubeValidator.ts:321 — primary: Joi.boolean().strict() |
✅ |
| At most one primary per dimension | CubeValidator.ts:337-339 — Only one link can be marked as primary |
✅ |
format: { type: link, label: … } |
CubeValidator.ts:116-123 formatAlternatives / formatSchema (type optional, label required) |
✅ |
Object form belongs under string dimensions |
formatSchema is the otherwise branch; time/number have their own schemas |
✅ correctly placed |
Anchors and link references — all resolve
| Reference | Target | Status |
|---|---|---|
/reference/data-modeling/dimensions#format (table.mdx:93) |
### \format`at reference:262` |
✅ |
/docs/data-modeling/dimensions#links (table.mdx:90) |
## Links at concept :382 |
✅ |
#cell-menu (table.mdx:92) |
## Cell menu at table.mdx:158 |
✅ |
#behavior (concept :411, :520) |
### Behavior at concept :504 |
✅ |
/docs/explore-analyze/charts/chart-types/table#links (concept :521) |
### Links at table.mdx:83 |
✅ |
[ref-workbooks] (3 new uses) |
defined at reference :1353 |
✅ |
The http/https/mailto restriction and the Style-tab picker behavior are Workbooks frontend, not present in this repo — taken on trust, as in earlier rounds.
Threads
All four of my earlier threads are resolved and outdated; nothing to re-affirm and nothing new worth an inline comment. The ## Display tab → ## Style tab anchor rename was flagged and accepted earlier — internally clean (zero display-tab references anywhere in docs-mintlify/); only external bookmarks land at the top of the page.
Style matches docs-mintlify/CLAUDE.md: surgical edits to existing pages, no padding, one canonical example per concept, screenshot placeholders in the page's established MDX-comment form, no "Cube Cloud" in newly written prose. Docs-only change — no security, performance, or test concerns.
Verdict: ready to merge.
• branch igor/cub-2253-render-values-as-links-docs •
Makes two documented promises about dimension links specific and true, now that Workbooks renders them.
links. The page said links "can be rendered as HTML links by supporting tools" without saying what that meant. It now states what actually happens: every link is available from the table cell context menu, and the link markedprimaryalso renders inline on the cell value.primary. The flag was accepted and validated (at most one per dimension) but never documented. It's now described whereiconandtargetare, and shown in the YAML example.format: link. The table entry now says the value itself is used as the URL, and documents the object form —format: { type: link, label: … }— which was already accepted but undocumented. Also notes that values outsidehttp,httpsandmailtorender as plain text.The table chart page's "Links" section described an older flow (picking a hidden URL column as the source) that doesn't match the product; it now describes declaring links in the data model and choosing which one renders.