Closed mi-col closed 1 year ago
The custom request function should only be aware of http specific information. Alternatively, You can parse the url and extract the language and namespace information there...
That's what I ended up doing, encoding them in loadPath
and parsing in request
, was simply wondering if a cleaner solution is possible.
Currently that's the only way. But If there are more users requesting this, we might do something...
No problem, thanks for clarifying
🚀 Feature Proposal
I would like to be able to have arguments of the
loadPath
function available as parameters in therequest
function.Motivation
In the case of unusual or strict APIs that don't fall under the url that can be constructed via the
loadPath
function, I would like to have its arguments be passed into the customrequest
function so that I can manage any scenario specific to the localization API that I am using.Example
In case the API I am using has strict requirements on multiple namespaces being passed in query params as
namespace=first&namespace=second
rather thanns=first+second
, if I retrieve different locales from different APIs or any other unusual scenario requiring a fine-tuned approach.