Integrate riverui queries into driver system, add Client.Schema() #983
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.
This integrates all of riverui's non-Pro queries into this library's driver system, which paves the way for riverui to support multiple driver backends (sqlite) and to add more Pro-specific UI extensions. These queries were generally imported as-is except for the sqlite variants which required some rework.
I also added a
Client.Schema()
accessor because I couldn't see any way for riverui to pull the schema from theriver.Client
in its constructor opts. Rather than add another param for it there, it seemed cleaner to just expose a reader method on the client. This all ends up being required if we want the UI to properly support custom schemas while also having it directly call into pilot and driver methods without having to expose all this functionality directly on theClient
and bloating its API.