Skip to content

FIX: Add getOwnValue method to MetaDataPropertyValue for fusion access - #15

Merged
bwaidelich merged 1 commit into
neos:feature/global-scope-metadata-propertiesfrom
c4ll-m3-j4ck:feature/global-scope-metadata-properties
Aug 4, 2026
Merged

bwaidelich merged 1 commit into
neos:feature/global-scope-metadata-propertiesfrom
c4ll-m3-j4ck:feature/global-scope-metadata-properties

Conversation

@c4ll-m3-j4ck

Copy link
Copy Markdown

No description provided.

@bwaidelich bwaidelich left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't need that change to make it work. Public properties are exposed to fusion

@bwaidelich

Copy link
Copy Markdown
Member

Sorry, wrong call – I had this patch applied in my branch by accident and it is required indeed because in Fusion metaDataPropertyValue.ownValue resolves to the hasOwnValue() method.

Maybe we can remove the hasOwnValue function instead – I don't think that this is required

@bwaidelich

Copy link
Copy Markdown
Member

Nah, let's just merge this, it doesn't do any harm!

@bwaidelich
bwaidelich merged commit 802aa88 into neos:feature/global-scope-metadata-properties Aug 4, 2026
@bwaidelich
bwaidelich self-requested a review August 4, 2026 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants