Repository navigation
Support request-aware template roots - #58
Merged
Merged
Conversation
dblock
force-pushed
the
fix/dynamic-template-roots-25
branch
from
October 27, 2026 02:37
847f581 to
c31531d
Compare
Danger ReportNo issues found. |
|
coverage: 100.0%. remained the same — dblock:fix/dynamic-template-roots-25 into ruby-grape:master |
Resolve configured roots in the current endpoint context, preserve explicit request roots, and isolate cached templates and layouts by resolved path. Keep static roots and unversioned paths unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
dblock
force-pushed
the
fix/dynamic-template-roots-25
branch
from
October 27, 2026 02:40
c31531d to
7ed6917
Compare
This file contains hidden or 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
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.
Changes
Support static configuration roots and zero-argument Proc/lambda roots evaluated in the current Grape endpoint context. Existing request roots take precedence, version directories remain opt-in, and fallback responses do not resolve templates. Cover per-request template/layout cache isolation and explicit resolver failures.
Validation
Local checks cover 41 examples, including version-specific templates and layouts with caching enabled and disabled, explicit request-root precedence, resolver errors, and formatter fallback. Hosted CI passes the full Ruby/Grape matrix and lint; Danger also passes.
Closes #25.
Created by Copilot, an AI, on behalf of @dblock.