T
TanStack•3h ago
rare-sapphire

No error upon defining conflicting routes

Why this does not trigger any errors: 
export const Route = createFileRoute('/server-routes')({
    server: {
        handlers: {
            GET: async ({ request }) =>
                new Response('Hello GET ' + request.url),
        },
    },
    component: () => (
        <QueryClientProvider client={queryClient}>
            <RouteComponent />
        </QueryClientProvider>
    ),
})
export const Route = createFileRoute('/server-routes')({
    server: {
        handlers: {
            GET: async ({ request }) =>
                new Response('Hello GET ' + request.url),
        },
    },
    component: () => (
        <QueryClientProvider client={queryClient}>
            <RouteComponent />
        </QueryClientProvider>
    ),
})
It clearly conflicts (page route and server route). In case of GET we get response, not a RouteComponent. And I guess it could be prohibited by allowind defining only one: either server.handlers.GET or component property
1 Reply
fair-rose
fair-rose•3h ago
this is allowed you can hand over from server route to component by calling next()

Did you find this page helpful?