You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to support arrays in the form sort=slug,id instead of sort=slug&sort=id. This is documented under swagger as the explode: false option of arrays (doc can be found here.)
After elysiajs/elysia-swagger#179 get merged, the explode parameter could be defined for swagger, but parsing won't work.
What is the feature you are proposing to solve the problem?
Either supporting specially the explode parameter or best support this syntax in all cases (or just close this issue and consider it a user-land feature ig.)
What alternatives have you considered?
Use a custom parser type with a t.Transform to manually convert a string to an array.
The text was updated successfully, but these errors were encountered:
What is the problem this feature would solve?
I'd like to support arrays in the form
sort=slug,id
instead ofsort=slug&sort=id
. This is documented under swagger as theexplode: false
option of arrays (doc can be found here.)After elysiajs/elysia-swagger#179 get merged, the explode parameter could be defined for swagger, but parsing won't work.
What is the feature you are proposing to solve the problem?
Either supporting specially the
explode
parameter or best support this syntax in all cases (or just close this issue and consider it a user-land feature ig.)What alternatives have you considered?
Use a custom parser type with a
t.Transform
to manually convert a string to an array.The text was updated successfully, but these errors were encountered: