Fix IContentBase.GetUdi()
extension method to support document-blueprint entity type
#16939
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.
Prerequisites
Description
While implementing document blueprint container support in Deploy 14, I noticed document blueprints (
IContent
withBlueprint = true
) were returning UDIs using the document entity type (e.g.umb://document/{GUID}
, instead ofumb://document-blueprint/{GUID}
).This PR adds tests for all supported entity types, fixes the issue and cleans up the
UdiGetterExtensions
class to remove redundant code. The added tests should be sufficient to verify the issue, but reverting to the first commit will show the failing test: