You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tracking issue for the version 3 syntax for rspc.
This syntax will come with a major change in the mental model. Instead of thinking about middleware and routers, you will think about procedures that are single operations. This aligns more with the tRPC v10 style of doing things and I think adopting the same patterns for rspc will make for a way better DX.
Queries
Mutations
Subscriptions
Middleware
Middleware context switching
Middleware args
Router merging
Replace TPrevMapper to TPrevMiddleware in public API
Error for duplicate procedure names -> using #[track_caller] to help
Store key as an array and not string ready for proxy syntax
Fix data_typekey when routing merging
Unit test duplicate procedure name error, and bindings exporting with complicated router
Validate procedure names and router prefix patterns
The tracking issue for the version 3 syntax for rspc.
This syntax will come with a major change in the mental model. Instead of thinking about middleware and routers, you will think about procedures that are single operations. This aligns more with the tRPC v10 style of doing things and I think adopting the same patterns for rspc will make for a way better DX.
TPrevMapper
toTPrevMiddleware
in public API#[track_caller]
to helpdata_type
key
when routing mergingRspcError
+ fix their docs cause they are wrong #49Once Full Send on v1 is active:
The text was updated successfully, but these errors were encountered: