Enable rack 3.0 #171
Merged
Enable rack 3.0 #171
Conversation
This file contains 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
mkon
force-pushed
the
rack-3.0
branch
3 times, most recently
from
064033e
to
581601d
Compare
mkon
force-pushed
the
rack-3.0
branch
3 times, most recently
from
e02797a
to
ba90486
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Test the gem with latest rack 3.0 while remaining compatible with 2.x.
Upgrade notes:
There is some places where the "rack response array" was replaced with an instance of
Rack::Response, most notablyApiValve::Forwarder#call. To compensate thisApiValve::Proxy#callcallsto_aon the result. I would recommend doing the same if you have any overrides in place, as this avoids most of the issues from a rack 3 upgrade.