We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
route
aot
1.1.23
Darwin 23.6.0 arm64 arm
You can create a simple server like this:
const app = new Elysia({ aot: false }) .get('/hi', ({ route }) => `Hello World ${route}`) app.listen(3000)
The route property in the context should not be undefined even when aot is set to false.
When you hit the endpoint, you should see Hello World undefined as the response. Setting aot to true will return Hello World /hi
Hello World undefined
Hello World /hi
The text was updated successfully, but these errors were encountered:
When aot is enabled the route is also missing at version 1.2.6
1.2.6
const app = new Elysia() .use( opentelemetry({ resource: otelConfig.resource, spanProcessors: [ new BatchSpanProcessor( new OTLPTraceExporter({ url: env.OTEL_EXPORTER_OTLP_ENDPOINT, }), ), ], }), ) .decorate("logger", logger) .use(swagger()) .use(notificationsApp) .get("/health", () => ({ status: "OK" })) .listen(3000);
Sorry, something went wrong.
No branches or pull requests
What version of Elysia is running?
1.1.23
What platform is your computer?
Darwin 23.6.0 arm64 arm
What steps can reproduce the bug?
You can create a simple server like this:
What is the expected behavior?
The route property in the context should not be undefined even when
aot
is set to false.What do you see instead?
When you hit the endpoint, you should see
Hello World undefined
as the response.Setting
aot
to true will returnHello World /hi
The text was updated successfully, but these errors were encountered: