validateSearch, so that the search params type will always be { email: string } (i.e. email is never null or an invalid email address).redirect in the validateSearch function itself, then this seems to be seen as a validation error and causes the error component to be triggered. If I don't throw the redirect, and instead just invoke it and don't return anything from validateSearch, then the return type of validateSearch now includes undefined as a possibility.redirect in the beforeLoad function for the route, though it seems that the search validation occurs before this, and since an error is thrown by the search validation, it will also trigger the error component first.null if validation fails), then redirecting from the route component based on whether it is null, but I feel like this would better be handled at the route definition level rather than the component.https://x.com/powersync_/status/2010721010006552775?s=20
dry-scarlet · 2mo ago
You can now submit your website/app/project to http://TanStack.com 's new showcase and have it seen by the TanStack community! - Global showcase browser - Per-library filters - Category filters Submit here: https://tanstack.com/showcase/submit View all here: https://tanstack.com/showcase
dry-scarlet · 3mo ago
TanStack AI Alpha 2 is here! 🖼️ Image, video, audio, speech, transcription, structured output 📦 Split adapters = smaller bundles, faster dev/contributions, easier 🎄 Fully tree shakable adapters ✨ Cleaner, flattened, fully type-safe APIs https://tanstack.com/blog/tanstack-ai-alpha-2
dry-scarlet · 3mo ago