feat: add model-level primaryKey support for dbt export #898
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.
Summary
This PR enhances the dbt export functionality to properly handle model-level primaryKey configurations in data contracts. The implementation differentiates between single-column and multi-column primary keys, applying
appropriate dbt constraints and tests.
Changes Made
Consultation Items
I also checked the export results after setting the PK at the column level, but nothing in particular was reflected.
Should this feature be removed?
Or should it be modified so that the NOT NULL and UNIQUE tests are set?
reviewee's checkpoint
pytest tests result
ruff check result
I haven't made the changes yet because there are still matters to discuss.