However, the data proxy seems to strip the query string. Unfortunately the apiKey in the query string is the only way to pass the token. Is there anyway to solve this problem?
I couldn’t find an example of plugin trying to set a query string value in a route.
I will test locally and see if I can figure out if this is a bug or not. The interpolation (replacing .SecureJsonData.apiKey with the value) should be supported but not sure if there is a good reason for the query string getting stripped or if it is a bug.
I’m happy to know that the auth will work with your PR. Thanks!
I noticed the the query string params are positional so the params has to be an array. One minor nitpick is there will be two “params” with different syntax e.g. the params for tokenAuth. That might be a bit confusing . “queryParams” or “urlParams” might be better? Just a suggestion.