Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PropertyPaths in Capabilities.NavigationRestrictions/RestrictedProperties #320

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

HeikoTheissen
Copy link

@HeikoTheissen HeikoTheissen commented Dec 11, 2024

<PropertyPath>One</PropertyPath>

This PropertyPath is invalid because it is evaluated relative to the type self.SinglePartKey of the annotated singleton. It is wrong to assume that it is evaluated relative to self.SinglePartKey/AllMany, despite the

<PropertyValue Property="NavigationProperty" NavigationPropertyPath="AllMany" />

The example has been corrected, but the XSL transformation seems to make the same wrong assumption (the OpenAPI file has changed after the correction). Somewhere here:

<xsl:variable name="navigation-non-sortable" select="$navigation-sortRestrictions/edm:PropertyValue[@Property='NonSortableProperties']/edm:Collection/edm:PropertyPath" />
<xsl:variable name="target-non-sortable" select="$target-sortRestrictions/edm:PropertyValue[@Property='NonSortableProperties']/edm:Collection/edm:PropertyPath" />
<xsl:variable name="non-sortable" select="$navigation-non-sortable|$target-non-sortable[not($navigation-non-sortable)]" />
<xsl:for-each select="$entityType/edm:Property[not(@Name=$non-sortable)]">

HeikoTheissen added a commit that referenced this pull request Dec 11, 2024
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.

1 participant