Routing failure when decoding API Gateway events

[SereneMatt]

Hello 👋

When using Open-Next's API Gateway converter, we are facing some issues with query parameters.

Issue:
API Gateway already decodes the query parameters for REST APIs as documented here. But the routing util here decodes the query parameters again causing routing failure at the converter.

We have a temporary workaround by using custom API Gateway converter where we encode the decoded query parameter 🙂. But this causes issues where we actually need some URL query parameters with decoded values.

Can this decoding be skipped for API Gateway events?

Thank you!

[conico974]

We don't do that anymore since #817
Should be fixed, please reopen if that's not the case