Currently, the query parameters of a HttpHandlerRequest take a single string as value. Since a url allows multiple values to be passed for the same key, we hould probably allow this (currently only the last value is stored). Moreover, parameters without a value are possible, but are currently stored as null.
We should accomodate these cases, either by adapting the type of tthe values in query, or by simply pasing a URLSearchparams object instead.
When released, the type change will be incompatible with dgt-platform-api, dgt-id-broker and semcom, so these should be updated.
Currently, the
query
parameters of aHttpHandlerRequest
take a single string as value. Since a url allows multiple values to be passed for the same key, we hould probably allow this (currently only the last value is stored). Moreover, parameters without a value are possible, but are currently stored as null.We should accomodate these cases, either by adapting the type of tthe values in
query
, or by simply pasing aURLSearchparams
object instead.When released, the type change will be incompatible with
dgt-platform-api
,dgt-id-broker
andsemcom
, so these should be updated.┆Issue is synchronized with this Wrike Task by Unito