Skip to content

Conversation

@briangregoryholmes
Copy link
Contributor

@briangregoryholmes briangregoryholmes commented Jan 7, 2026

This PR is a rough demonstration of the structure necessary to move from Orval to connectrpc and, in turn, refactor our runtime context following the exploration in the discussion here: #8590.

For illustrative purposes, this PR specifically replaces the metricsViewAggregation and metricsViewTimeSeries queries used in the Leaderboard and MetricsTimeSeriesChart components respectively, highlighting usage of the suggested pattern both inside and outside of components.

Non-exhaustive to do list:

  • Consider moving Project and client creation out of ProjectProvider and into a load function
  • Scheduled project refetching
  • Refetching of expired tokens
  • Rough check of ProjectProvider structure to ensure it allows for arbitrarily switching between projects as well as rendering dashboards from two separate projects simultaneously
  • Flesh out ProjectManager class
  • Get input from platform about backend code gen (this PR is more about frontend consequences)
  • How do we get code gen for the TanStack queries? May not be sustainable to do this manually, but there is no preexisting code-gen solution. See discussion here: feat: Extend connect-query-es to other Tanstack Query variants connectrpc/connect-query-es#324

@briangregoryholmes briangregoryholmes self-assigned this Jan 7, 2026
@briangregoryholmes briangregoryholmes changed the title feat: connect rpc poc feat: connectrpc and runtime context poc Jan 7, 2026
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.

2 participants