dbt-constraints-docs

[sungchun12]

Description & motivation

To-do before merge

• Ensure PR #6271 is merged
• Update migration guide specific to 1.5
• Update version blocks for 1.5

Prerelease docs

If this change is related to functionality in a prerelease version of dbt (delete if not applicable):

• I've added versioning components, as described in "Versioning Docs"
• I've added a note to the prerelease version's Migration Guide

Checklist

If you added new pages (delete if not applicable):

• The page has been added to website/sidebars.js
• The new page has a unique filename

[netlify]

✅ Deploy Preview for docs-getdbt-com ready!

Name	Link
🔨 Latest commit	f98639a
🔍 Latest deploy log	https://app.netlify.com/sites/docs-getdbt-com/deploys/63ee8365c937df0008bc5319
😎 Deploy Preview	https://deploy-preview-2601--docs-getdbt-com.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[b-per]

As this relates to models only, would it make sense to move it under "for modes", either as a subitem or in "Model Configurations"?

We should also add the ability to set constraints_enabled to the "General configurations" part of the docs for models.

[sungchun12]

@b-per good call out. I'll make that change for section placement!

[sungchun12]

I was about to move the entire constraints_enabled page as a subsection under model configs, but then realized it gets cluttered and makes it hard to discover this information in the first place. I opted to create hyperlinks in the model configs page to the constraints_enabled page to make it easier to digest all the information in one place.

[sungchun12]

I'll wait to merge this closer to 1.5's release as many open issues may be complete and alter how contracts look and feel.

[jtcohen6]

@sungchun12 Thanks for the strong start here! Mind if I take over these docs from you? I want to take a swing at standing up the "wireframe" for model contracts — something we can share with devs and early beta testers alike — while also calling out the renaming & syntax changes that we have in the pipe.

[sungchun12]

@jtcohen6 go ahead and thanks for asking!

[jtcohen6]

I'm going to merge this into a new branch (jerco/model-contracts) so I can keep working on it there!