feat: raise Errors::UnknownView for missing render view#589
Open
SAY-5 wants to merge 1 commit into
Open
Conversation
lessthanjacob
approved these changes
Jun 23, 2026
Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
SAY-5
force-pushed
the
feat-missing-view-error
branch
from
f5fe1c4 to
f847800
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
2 participants
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.
Adds
Blueprinter::Errors::UnknownView, raised byRendering#hashifywhen the requested view does not exist. It inherits fromBlueprinterErrorso existing rescue blocks keep working, and lets callers distinguish a 400 (caller-supplied bad view name) from a 500 (any otherBlueprinterError). This ports the V2 class forward as suggested in #569.Closes #569
Checklist: