rspc v3 syntax #628
Closed
rspc v3 syntax #628
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Ignored Deployments
|
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.
This is an experimental branch using the alpha version of the rspc v3 syntax. It also comes with the new version of Specta which provides stupidly better error handling and a large number of bug fixes.
I spent the weekend working with @Brendonovich on this and we have got some stuff working which will greatly help with the maintainability of our rspc integration as it means we can remove all uses of private rspc APIs (of which we have a lot). Currently, it takes me 2-6 hours of updating Spacedrive when rspc does any non-minor changes which is pretty bad.
These changes also come with a shift in the mental model which should make more sense and allow us to make better use of middleware which will help to solve many challenges such as authentication as we get further into launching our product.
TODO: