V14: Fix null ref exception in current user permission endpoint#16286
Merged
V14: Fix null ref exception in current user permission endpoint#16286
Conversation
Zeegaan
added
release/14.0.0-rc4
and removed
project/bellissima
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.
Given an invalid content key, the current user endpoint currently throws a null ref exception, this is because the entity gotten from the entity service is null, I've added a guard that prevents this, and instead returns a 404, aligning with the document and media versions of the endpoint.
Testing
The
/umbraco/management/api/v1/user/current/permissionsshould not throw a null ref exception when given an invalid guide, but instead a not found.