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
Now that we're supporting fancy parameter parsing (e.g. style=deepObject etc), it would be helpful for the application to not have to do the parsing all over again and just use the values that we parsed.
This could be passed back in the config hashref that is used in all methods:
I don't know if there's a need to include headers in here as they are parsed very simply, and the rules do often change depending on the header. query parameters are the ones that are tricky here.
Perhaps we only want to do this on demand, or only when a special style is used.
The text was updated successfully, but these errors were encountered:
This would also be helpful when parsing multipart objects - the application can just use the hashref form that we already validated against the schema.
We can do this by making the user pass a specific key in the $options hash - if it is present, we will populate/overwrite it with the parsed data, and otherwise we won't, because this will consume a lot of memory.
Now that we're supporting fancy parameter parsing (e.g. style=deepObject etc), it would be helpful for the application to not have to do the parsing all over again and just use the values that we parsed.
This could be passed back in the config hashref that is used in all methods:
I don't know if there's a need to include headers in here as they are parsed very simply, and the rules do often change depending on the header. query parameters are the ones that are tricky here.
Perhaps we only want to do this on demand, or only when a special style is used.
The text was updated successfully, but these errors were encountered: