Repository navigation
Add stubs for resolvers - #1557
Merged
Merged
Conversation
reyammer
approved these changes
Oct 23, 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 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.
CC @corkamig
The flow is:
There is still one thing to be done, but it can be done later since it needs KB synchronization: the same way we have a column for "supported by the model" and "supported by the rules" for each content type, we also want a column for the resolvers. I think the simplest way to do it is to have a
rust/gen/resolvers/content_typesthe same way we haverust/gen/rules/content_typesexcept it would be manually edited instead of autogenerated.