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, you can get the response XML via to_xml and you can get the request XML via Operation#request (#620).
I want to be able to filter the data on these. I was thinking of creating some type of scrubber and saw that Savon already has this ability.
How about optionally scrubbing the output of the request and response like so:
response=savon_client.call(...)response.to_xml(filter: true)response.request.to_xml(filter: true)# currently you have to call response.request.body to get the XML body. This feature would add a new method to SOAPRequest called `to_xml`
As you could probably tell, passing filter: true would filter the XMLs returned based on the filters defined.
I can implement this feature.
The text was updated successfully, but these errors were encountered:
I must apologize for taking so long to respond to your issue, @ramontayag, I honestly didn't mean to wait so long to collect my thoughts here.
Thanks for your interest @ramontayag but I don't believe this functionality belongs in Savon itself. For logging, I can understand that users may want to avoid logging sensitive information (e.g.: usernames and passwords) via Savon, but I don't believe that filtering the actual response is a feature that is desirable here. More often than not, this should belong in your actual application, or some adapter that you wrap around Savon.
Currently, you can get the response XML via
to_xml
and you can get the request XML viaOperation#request
(#620).I want to be able to filter the data on these. I was thinking of creating some type of scrubber and saw that Savon already has this ability.
How about optionally scrubbing the output of the request and response like so:
As you could probably tell, passing
filter: true
would filter the XMLs returned based on thefilters
defined.I can implement this feature.
The text was updated successfully, but these errors were encountered: