Allow configuration overrides from request options #111
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.
In my own projects I was required to change the configuration on request basis. For example you have
/api/v1
which uses a different header name for the page than/api/v2
. Using a configuration block in a before action likeis not thread safe and will thus not work on servers like
puma
. Therefore I've added the option to override configs through the paginate options hash. In theory you can even change the paginator between requests.Hope you like the idea!