Remove Grape::Http::Headers #2554
Merged
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.
This PR removes
Grape::Http::Headers. Since most constantsHTTP_were just literal string and Grape's uses#frozen_string_literal: true, it made sense to just use the literal string wherever needed. Here's a list of notable changes:Grape::Http::Headers::SUPPORTED_METHODShas been moved toGrapemodule.Grape::Http::Headers::HTTP_HEADERShas been moved toGrape::Requestand its now calledKNOWN_HEADERS. The last has been revisited to reflect Rack 3's KNOWN_HEADERS. Its not an exact copy. Grape's version has more.Grape::Util::Lazy::Objectno longer exists. Solely used byGrape::Http::Headers::HTTP_HEADERSGrape::Http::Headers.find_supported_methodno long exists. It wasn't used.to_swhen callingheaderssince its not just a plain{}but aGrape::Util::Headers. Fix Grape allows invalid headers to be set. #2334