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
Currently when a body/payload is supplied to Pode, the inbuilt parsers are XML, CSV, JSON, Form, and MultiForm.
It would be nice to support custom parsers - to not only add parsers for new content type, but also override the inbuilt ones.
Add-PodeBodyParser-ContentType 'text/yaml'-ScriptBlock {
param($body)
# some logic to parse itreturn$parsed_body
}
plus a:
Remove-PodeBodyParser-ContentType 'text/yaml'
So just before the ConvertFrom-PodeRequestContent internal function is about to parse, it checks some map of custom parsers for the content type first.
Additional Context
This could to open the way for Pode extensions - like a Pode-Yaml parser, etc.
The text was updated successfully, but these errors were encountered:
Describe the Feature
Currently when a body/payload is supplied to Pode, the inbuilt parsers are XML, CSV, JSON, Form, and MultiForm.
It would be nice to support custom parsers - to not only add parsers for new content type, but also override the inbuilt ones.
plus a:
So just before the
ConvertFrom-PodeRequestContent
internal function is about to parse, it checks some map of custom parsers for the content type first.Additional Context
This could to open the way for Pode extensions - like a Pode-Yaml parser, etc.
The text was updated successfully, but these errors were encountered: