Support inserting middleware before/after anonymous classes in the middleware stack #1479
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.
I realised that this commit broke usages of
insert_before
/insert_after
withGrape::Middleware::Error
. For example, this is how I use it:Since that commit,
Grape::Middleware::Error
is inserted in the middleware stack asClass.new(Grape::Middleware::Error)
. Then, when we try to insert another middleware before or after it, we get:The reason is that we don't recognize the anoymous class that represents
Grape::Middleware::Error
in the stack. This pull-request allows considering the superclass for anonymous classes when comparing middleware within the stack. Feel free to suggest a different way to approach this problem, this was just my personal attempt to fix it in a simple way.