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
$ curl https://testnet.superhero.aeternity.art/tokenCache/wordRegistry\?search\=yatt+2
{"message":"Parameter 'search' must be url encoded. Its value may not contain reserved characters.","errors":[{"path":".query.search","message":"Parameter 'search' must be url encoded. Its value may not contain reserved characters."}]}%
Seems that it is correct to use + in query, at least URL class encodes it this way:
Current behavior:
Seems that it is correct to use
+
in query, at leastURL
class encodes it this way:as a workaround proposing to set
allowReserved: true
as proposed in cdimascio/express-openapi-validator#300The text was updated successfully, but these errors were encountered: