best practice for invalidating protected queries upon profile switch
I have an app where users can have multiple profiles. I have a protectedProcedure that does a db check on the user and profile ownership as a base.
on the frontend, once user switches profile, I want to invalidate all queries that are "protected".
Well known option is:
Above will work but switching profile may not always happen in one spot, or through an explicit call. Server might also return a response that may switch the user's profile.
previously to tRPC, I have done attached the userId to the query key to "protected" queries like
But this is manual and requires me to add an arbitrary
I also thought about using
Any suggestions here?
on the frontend, once user switches profile, I want to invalidate all queries that are "protected".
Well known option is:
Above will work but switching profile may not always happen in one spot, or through an explicit call. Server might also return a response that may switch the user's profile.
previously to tRPC, I have done attached the userId to the query key to "protected" queries like
queryKey: [arg1, arg2, userId, currentProfileId]queryKey: [arg1, arg2, userId, currentProfileId], which ensured revalidation upon switching through any measure.But this is manual and requires me to add an arbitrary
.input().input() to the protectedProcedureprotectedProcedureI also thought about using
queryHashKeyFnqueryHashKeyFn at the global level, but can get finicky with SSR/Suspense and feels too hacky, and not to mention it will invalidate ALL, not just protected.Any suggestions here?
