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
We are making a number of breaking changes in #236 to make the naming of config parameters more consistent. Is it worth making a bunch of breaking changes to the API to make the field names more consistent as well? For example, http_endpoint could be http_server_url and btp_uri could be btp_server_url
The text was updated successfully, but these errors were encountered:
I'm fine with that. Let's also use that PR as a chance to split out the btp_uri into btp_outgoing_token and btp_server_url (to avoid having to prefix the URI with credentials)
We are making a number of breaking changes in #236 to make the naming of config parameters more consistent. Is it worth making a bunch of breaking changes to the API to make the field names more consistent as well? For example,
http_endpoint
could behttp_server_url
andbtp_uri
could bebtp_server_url
The text was updated successfully, but these errors were encountered: