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
1.1.15
Darwin 23.6.0 arm64 arm
import { treaty } from '@elysiajs/eden'; import { expect, test } from 'bun:test'; import Elysia, { t } from 'elysia'; test('accepts optional query params with optional number', async () => { const repro = new Elysia().get('/repro', () => 'works', { query: t.Object({ string: t.Optional(t.String()), boolean: t.Optional(t.Boolean()) }), }); const api = treaty(repro); const { error } = await api.repro.get({ query: { string: 'asd' } }); expect(error).toBeNull(); });
The optional boolean would be optional
schema validation error
This has been introduced in 1.1 with the new schema validation coercion feature.
node_modules
bun.lockb
yes
The text was updated successfully, but these errors were encountered:
#907 seems to fix it
Sorry, something went wrong.
🔧 fix: #907, #872, #926, #929, #912
e7dfe29
No branches or pull requests
What version of Elysia is running?
1.1.15
What platform is your computer?
Darwin 23.6.0 arm64 arm
What steps can reproduce the bug?
What is the expected behavior?
The optional boolean would be optional
What do you see instead?
schema validation error
Additional information
This has been introduced in 1.1 with the new schema validation coercion feature.
Have you try removing the
node_modules
andbun.lockb
and try again yet?yes
The text was updated successfully, but these errors were encountered: