Add a bindings field for implementations in other languages - #421
Merged
Merged
Conversation
grst
approved these changes
Sep 22, 2026
Member
Author
|
Ah whops, I had wanted to think about and iterate on this before merging but if both of you like this version already then uhm let's ship it haha. Thanks |
Member
|
Haha I do. I guess I’d have expected the “draft PR” mode if it was to be iterated on. |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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
bindingsfield to the schema: a list of{language, name, url}for implementations of a package's objects or on-disk format in other languages, restricted to ones maintained under the scverse org.languageenum moves to$defsso the package's own language and a binding's language stay in sync.project_homeand the rest.Ran
validate-registrylocally: all three URLs validate,packages.jsoncarries the field, pre-commit passes.