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.
Fix routes memoization
Base:
master
Branch:
fix_routes_memoization
Summary
Ensure
routes
memoization works reliably by makingroutes
a non-overridable method and tightening specs to verify the memoization behavior directly.Motivation / Context
routes
method was eligible to be overridden, which could inadvertently break memoization and force repeated route computation.Changes
routes
non-overridable to preserve memoization guarantees.Implementation Notes
routes
as a non overridable methods so that memoization works properly. Added a better specs so that a private method is not expected and memoization is really tested. (Eric Proulx)Files Changed (4)
lib/grape/api.rb
lib/grape/api/instance.rb
lib/grape/dsl/routing.rb
spec/grape/dsl/routing_spec.rb
Diff Stats
4 files changed, 15 insertions(+), 18 deletions(-)
Testing
spec/grape/dsl/routing_spec.rb
to validate memoization behavior.bundle install
bundle exec rspec spec/grape/dsl/routing_spec.rb
bundle exec rspec
Backwards Compatibility / Risk
routes
. Marking it non-overridable is intentional to protect memoization semantics.Checklist
routes
non-overridableNotes for Reviewers
routes
is protected from overriding and how tests assert memoization without relying on private methods.