Add tRPC, use it for group expenses, balances and information page #246
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
scastiel
changed the title
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 PR bootstraps a tRPC API for the project. The idea is to progressively move all the calls to the database in this API for better separation of concerns.
When this migration is finished:
Note that it doesn't necessarily means leaving React Server Components, as it is totally possible to call a tRPC API from the server. But with the goal of making the app usable offline, we might make it client-only.
This PR also uses the new tRPC API for the expense list, balances and group information page,. It handles pagination (infinite scroll) as well as filtering on the server (so that the API returns only the matching expenses).