Move middleware setup to after calling super #138
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Seems like teamsnap_rb 3 is not working on fresh installs.
to reproduce
results in :
To troubleshoot, I first tried to reproduce with a curl request directly against the API, but that still works fine.
After adding a proxy server, I noticed that the gem isn't setting the
Authorization
header. In looking further, I noticed most middleware examples set options after super. Looking at the history of the baseFaraday::Middleware
class I found this change added@options
to the base class which overwrites the auth middleware's options when super is called last.sorry, didn't write a spec, I'll leave that you all 馃槃