Which Umbraco version are you using?

16.0.0

Bug summary

I've followed examples about using property editors in my own views using <umb-property-dataset ...> with a child element <umb-property property-editor-ui-alias="Umb.PropertyEditorUi.Tags" ...>

The Property Editor is displayed, and value updates can be handled but the Tags Property Editor never offers matches/suggestions despite passing in and confirming the group has been specified.

Looking at the code this is fundamentally happening inside the umb-tags-input component at the following location because this.culture is undefined.

It appears the umb-property-dataset uses Invariant culture which is essentially null. Looking at the Tags Repository, Data Source code, and the management API it looks like a null culture value is allowed, so the check for undefined culture isn't required?

Specifics

No response

Steps to reproduce

Inside a custom component render the following element structure.

<umb-property-dataset ...>
    <umb-property property-editor-ui-alias="Umb.PropertyEditorUi.Tags" ...>
    </um-property>
</umb-property-dataset>

When this component is shown in the back-office suggestions are not provided for the property editor.

Expected result / actual result

Suggestions should be provided as normal.