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
This issue tries to describe two problems: one with the developer experience and one with the functionality of the CDK.
I specify a stream whose base_url is https://api.congress.gov/v3 and whose path is /bills.
when running the command, it resulted in some failures in both check and read. --debug mode revealed that we were actually making the HTTP request to https://api.congress.gov/bills not https://api.congress.gov/v3/bill. Changing the path to bill (removing the leading /) resulted in making the request to the correct URL.
I get that this is the "technically" correct behavior of the urlparse python method that we're using under the hood, but even then it was a fairly confusing experience. Really, i would have just guessed that url_base and path are concatenated and the double slashes are removed, that's it. No extra magic.
Expected Behavior
Instead of the current behavior, concatenate url_base and path and remove double forward slashes from the result. That comprises the full URL.
Current Behavior
This issue tries to describe two problems: one with the developer experience and one with the functionality of the CDK.
I specify a stream whose base_url is
https://api.congress.gov/v3
and whose path is/bills
.when running the command, it resulted in some failures in both
check
andread
.--debug
mode revealed that we were actually making the HTTP request tohttps://api.congress.gov/bills
nothttps://api.congress.gov/v3/bill
. Changing the path tobill
(removing the leading/
) resulted in making the request to the correct URL.I get that this is the "technically" correct behavior of the
urlparse
python method that we're using under the hood, but even then it was a fairly confusing experience. Really, i would have just guessed thaturl_base
andpath
are concatenated and the double slashes are removed, that's it. No extra magic.Expected Behavior
Instead of the current behavior, concatenate
url_base
andpath
and remove double forward slashes from the result. That comprises the full URL.My full YAML configuration for reference was:
The text was updated successfully, but these errors were encountered: