Is there a “canonical” way to handle the situation...
# singer-tap-development
s
Is there a “canonical” way to handle the situation @stephen_lloyd brings up here: https://meltano.slack.com/archives/C01PKLU5D1R/p1618198759035800 i have ported a couple taps over now and have implemented the
response_result_key
approach i describe here. would be happy to submit a pr if we think that would be good. Maybe the more flexible way would be something like
response_path = 'teams'
or
response_path = 'data.teams'
to parse a json structure.
e
response_path
using a jsonpath would be a nice approach. Default would be something like
$[*]
?
a
@stephen_lloyd - Thanks for logging this here. I think you’ve got the right approach with
parse_response()
, in terms of what we support today. I do really like the suggested
response_path
approach though as you and @edgar_ramirez_mondragon are suggesting. Do either of you want to create an issue for this, and/or kickoff an MR? I had not considered the
response_path
approach but if there’s a stable+robust implementation, we could make that the default implementation if
parse_response()
is not overriden.
e
I can kickoff the MR simple smile