Open oscartbeaumont opened 2 years ago
Future:
selection!
macro add abritary values Eg. selection!(user, { __type: "user", name, email });
- This would be cool but may not be possibleselection!
macro subselection Eg. selection!(userWithPets, { name, email, pets: { name, email });
Long Term:
tokio
from dependencies if possibleuseBridgeQuery
and useLibraryQuery
to automatically handle injecting the library id. This shouldn't be such a burden on end application developers.v0.0.5:
Config
defined on a subrouter when merging. Warning when mounting multiple Config
's.Arc
+ Mutex
to get state into rspc. Contrast with Axum and Actix-web approaches to state.Future:
Document using a Cargo Alias to run the unit test
Next release plans:
ctx.invalidateQuery
Documentation Site v3 Upgrades:
impl Serialize + Type
impl GenericRouter
to fix the Spacedrive problem of returning routersCow
or trie routermw.middleware
should be shorten to mw(...)
like what is done for procedures
Pre open-source:
Spacedrive Features:
CompiledRouter
toRouter
andRouter
toRouterBuilder
+ GiveCompiledRouter
a set of default genericsselection!(x, { field_one, field_two })
macroselection!
macro on listsHandling tenants or libraries. I am thinking maybe the ID comes from the request context but how would the frontend inject context. Maybe something on client but that has React context???trpc
compatibility to clean up code + typescript support for error handlingFixes:
&'static str
I think it needs ats_rs::TS
impl