[pull] master from cube-js:master - #666
Merged
Merged
Conversation
…ting (#11561) * docs(dbt): explain per-model schema resolution and the dbt target setting The dbt integration page described the schema as a single value you configure, which was never quite true and is actively misleading for projects whose models build into several schemas. Generated cubes take their schema per model, from whatever dbt resolved for that model. The troubleshooting entry for "a generated cube points at the wrong table or schema" was the worst of it: it told you to check that the schema field matches where your models land, which is the one thing that isn't the cause. - New "Models in several schemas" section: schemas resolve per model, plus a table of what `+schema: analytics` becomes under dbt's default `generate_schema_name` (`<target schema>_analytics`) versus a production override (`analytics`). - Warning that a `{% if target.name == 'prod' %}` override REQUIRES setting the dbt target — otherwise the macro takes its fallback branch and every model collapses onto the target schema, which is exactly how a multi-schema project ends up with every cube pointing at one schema. - Connection fields: "dbt models schema" is now "dbt target schema", described as the default for models that don't declare their own, and the optional "dbt target" field is documented. - "What gets generated" now states that the schema segment of `sql_table` is per model. - Troubleshooting rewritten symptom-first: all cubes on one schema (set the target), all cubes prefixed (dbt's default, working as documented), one cube wrong (that model's own config). Matches the console-ui field labels and behavior. * docs(dbt): correct the dbt target description, drop a dangling anchor Review feedback on #11561. - **dbt target row was misleading.** It said the name matches "an output in your dbt project", which would send readers looking for a profiles.yml that Cube never reads: the pull generates its own profile in a sandbox (`<project>/.profiles/profiles.yml`) with a single output named after this field, and `dev` is Cube's default when the field is blank — not the `target:` key from a committed profiles.yml. Reworded to say the name doesn't have to match anything in the repository, and that what it actually does is set `target.name` for `generate_schema_name`. - **Dropped the "No custom schemas anywhere" table row.** Its cell was "(n/a)", which contradicted the column asking what `+schema: analytics` resolves to. The point it carried is already in the paragraph above. - **Removed an anchor to an Accordion title.** Mintlify only generates heading slugs for ##/###, so the link was a no-op; the entry is now named in prose. My original anchor check matched accordion titles as if they were headings, which is exactly why this got through — re-verified with headings only, and all nine remaining in-page anchors resolve.
* docs: document multi-select and group move/delete of dashboard widgets * Update docs-mintlify/docs/explore-analyze/dashboards/widgets/index.mdx Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> * docs(dashboards): mark multi-select & group actions as preview (CUB-3818) --------- Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
* docs(dashboards): document Spacer & Divider layout widgets Add a Spacer & Divider page under dashboard Widgets covering the two non-data layout elements (CUB-3039): a resizable spacer that is invisible on published dashboards, and a fixed non-resizable divider line. Both follow the dashboard widget styling settings. Link the new page from the widgets index and add it to the nav. * docs(dashboards): address review — reconcile toolbar wording, tighten layout page - Update text.mdx and ai-summary.mdx to the consolidated 'Add Widgets' toolbar menu (CUB-3039 reorganized the per-type insert buttons), so they no longer contradict the widgets index. - Drop the duplicated 'invisible on the published dashboard' clause from the spacer styling bullet (already stated above). - Remove the vague removal instruction from the layout page. * docs(dashboards): mention layout elements in widgets intro + taxonomy Address non-blocking review nits: add layout elements (spacer/divider) to the widgets index frontmatter description and intro paragraph so they stay in sync with the widget list, and add a Layout entry to the widget taxonomy in docs-mintlify/CLAUDE.md. * docs(dashboards): mark Spacer & Divider as preview (CUB-3039) * Update filter widget and time grain terminology
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )