UFM: Add umbMemberName component (closes #22147) - #23165
Merged
Merged
Conversation
This is to support the standalone Member Picker values.
umbMemberName component (closes #22147)
leekelleher
marked this pull request as ready for review
June 18, 2026 14:01
This comment was marked as resolved.
This comment was marked as resolved.
AndyButland
reviewed
Jun 18, 2026
AndyButland
left a comment
Contributor
There was a problem hiding this comment.
Tests out as expected @leekelleher:
I've also verified:
- Multiple members
- UDI syntax
- MNTP output
As per the other PR - looks like we have marked-ufm.test.ts used to test various components, including umbContentName. Should a test for this be added there too?
I added the "needs docs" label as this component should be documented here (and for 18).
Member
Author
|
Thanks @AndyButland! Added two parsing tests for re: docs. I'll follow-up with a docs PR. |
AndyButland
approved these changes
Jun 19, 2026
AndyButland
enabled auto-merge (squash)
June 19, 2026 09:08
8 tasks
This was referenced Jul 28, 2026
Closed
This was referenced Aug 1, 2026
This was referenced Aug 9, 2026
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.
Description
Fixes #22147.
Adds a new
{umbMemberName:alias}UFM (Umbraco Flavored Markdown) component that resolves a Member Picker property value to the member's display name.Why a dedicated component?
{umbContentName}already importsUmbMemberItemRepositorybut defaults to the document entity type when the value has notype/mediaKeydiscriminator. A Member Picker persists a bare GUID — ambiguous without the marker to signal intent — so a separate marker is the correct design.Value structure support
The component resolves member references regardless of how they are stored, handling each of the following (as a single value or an array):
"3f2504e0-4f89-11d3-9a0c-0305e82c3301""guid1,guid2"umb://member/{GUID}{ type, unique }(whereuniquemay itself be a GUID or UDI)Names are joined by
,when multiple members resolve.Known duplication (intentional)
The observe/alias-extraction logic is structurally similar to
content-name.element.ts. A shared base was considered and deferred — if a third name-resolving UFM component appears, that's the moment to extract it.Steps to test
alias: memberPicker) to a document type.{umbMemberName:memberPicker}.