Uh oh!
There was an error while loading. Please reload this page.
feat: export ValidateEntries for composing wrappers - #31
Merged
Conversation
commit: |
spydon
approved these changes
Aug 26, 2026
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Renames the engine's private
Validatetype toValidateEntriesand exports it from the package root and core subpath, documented for public use. The type takes a seed context parameter, so a composing wrapper that puts its own keys on the context before an entry array runs (the waywithSupabasedoes in@supabase/server) can validate entry prerequisites and key collisions at compile time, exactly aspipelinedoes. Type-only change with no runtime behavior; new tsc-verified tests pin the exported type's satisfied-prerequisite, missing-prerequisite, and key-conflict cases.