Skip to content

fix: elysia should utilize ctx.query vs. request.searchParams #452

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ymc9 merged 1 commit into from
Nov 30, 2025
Merged

fix: elysia should utilize ctx.query vs. request.searchParams #452

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions packages/server/src/adapter/elysia/handler.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ export interface ElysiaOptions<Schema extends SchemaDef> extends CommonAdapterOp
export function createElysiaHandler<Schema extends SchemaDef>(options: ElysiaOptions<Schema>) {
return async (app: Elysia) => {
app.all('/*', async (ctx: ElysiaContext) => {
const { request, body, set } = ctx;
const { query, body, set, request } = ctx;
const client = await options.getClient(ctx);
if (!client) {
set.status = 500;
Expand All @@ -35,7 +35,6 @@ export function createElysiaHandler<Schema extends SchemaDef>(options: ElysiaOpt
}

const url = new URL(request.url);
const query = Object.fromEntries(url.searchParams);
let path = url.pathname;

if (options.basePath && path.startsWith(options.basePath)) {
Expand Down
Loading