Skip to content

revert: remove CheckScopedForeignKey node type (replacing with scoped field design)#1279

Merged
pyramation merged 2 commits into
mainfrom
feat/revert-check-scoped-fk
Jun 7, 2026
Merged

revert: remove CheckScopedForeignKey node type (replacing with scoped field design)#1279
pyramation merged 2 commits into
mainfrom
feat/revert-check-scoped-fk

Conversation

@pyramation
Copy link
Copy Markdown
Contributor

Summary

Reverts the CheckScopedForeignKey node type registration from #1278. Restores DataDenormalized which was part of the same merge.

Why: The standalone CheckScopedForeignKey node type (requiring manual references[] configuration) is being replaced by a simpler scoped boolean on metaschema_public.field. The new design auto-generates validation triggers from field metadata without needing a separate node type entry.

DataDenormalized is preserved — it was incorrectly caught in the merge revert and is re-added in a follow-up commit.

Link to Devin session: https://app.devin.ai/sessions/12842f98263d4815b6713291efc825ad
Requested by: @pyramation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@pyramation pyramation merged commit 724e07e into main Jun 7, 2026
35 checks passed
@pyramation pyramation deleted the feat/revert-check-scoped-fk branch June 7, 2026 05:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant