update the docs for per request config#338
Merged
UlisesGascon merged 1 commit intomasterfrom Jun 5, 2025
Merged
Conversation
bjohansebas
approved these changes
Nov 27, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
We get issues occassionally asking about how to do per route configuration of various sorts.
We do support this, but the readme doesn't do a good job of signaling.
Updated the readme to make it clearer, and tweaked the example to show a more appropriate example. The previous example can be accomplished by passing a function as the
originoption, the updated example shows settingcredentialsbecause that is the only way to set it per request currently.