-
Notifications
You must be signed in to change notification settings - Fork 45
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
All NavigationPropertyRestriction
s nullable
#286
All NavigationPropertyRestriction
s nullable
#286
Conversation
@@ -272,16 +272,16 @@ supported: | |||
<Property Name="SortRestrictions" Type="Capabilities.SortRestrictionsType"> | |||
<Annotation Term="Core.Description" String="Restrictions on orderby expressions" /> | |||
</Property> | |||
<Property Name="TopSupported" Type="Edm.Boolean" Nullable="false" DefaultValue="true"> | |||
<Property Name="TopSupported" Type="Edm.Boolean"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<Property Name="TopSupported" Type="Edm.Boolean"> | |
<Property Name="TopSupported" Type="Edm.Boolean" Nullable="true"> |
Better state explicitly that we mean it and didn't just forget it.
And maybe describe what null/omission means.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better state explicitly that we mean it and didn't just forget it.
Only for these two, or also for all others?
And maybe describe what null/omission means.
Isn't that already said?
<Annotation Term="Core.LongDescription" String="Restrictions specified on an entity set are valid whether the request is directly to the entity set or through a navigation property bound to that entity set. Services can specify a different set of restrictions specific to a path, in which case the more specific restrictions take precedence." /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All four that were touched in this PR, please
TC 2025-01-22 decided against this incompatible change. |
This reverts commit 910d724.
Fixes oasis-tcs/odata-openapi#322