-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request - ability to use custom faraday middleware #424
Comments
Hi - this will be added in the next release. Will post in this thread once it's released.
|
Just in case you need another example, I believe my team is also blocked on upgrading from v13 to v15 because of this. Here's is our setup: client = ::Plaid::Client.new(config) do |builder|
# Log responses, which will include the request_id needed by Plaid support.
# This needs to come before the Plaid connection setup below because that will set
# the adapter, which must be the last middleware in Faraday, otherwise it complains.
builder.use :instrumentation, name: 'request.plaid'
::Plaid::Client.build_default_connection(builder)
# Set a custom timeout that may be configured differently between web & background requests.
builder.options[:timeout] = Rails.configuration.x.plaid_request_timeout
end |
Hi sorry for the delayed response |
@vorpus Yes the new documentation in the README to use |
works for me as well, thanks for update |
@vorpus maybe provide some more examples similar to that of @ctlevi to help people through the upgrade path
|
In our application, we use inhouse faraday middleware called RequestMetricsMiddleware to instrument all outgoing request. It would be great if user of library can use custom middleware like below
The text was updated successfully, but these errors were encountered: