TopSupported and SkipSupported non-nullable with DefaultValue="true" #323
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.
Fixes #322
Assume an entity set of singleton$S$ with a non-containment navigation property $p$ and a navigation property binding of $S/p$ to the entity set or singleton $T$ .
If$S$ is annotated with ${}=p$ but without $S/p$ supports $T$ . Analogous for
Capabilities.NavigationRestrictions/RestrictedProperties
annotation withNavigationProperty
TopSupported
, the default valueTopSupported=true
is implied and hence the resource path$top
, regardless of any annotationCapabilities.TopSupported
onSkipSupported
.The$S$ it evaluates $T$ , ignoring the default value.
V4-CSDL-to-OpenAPI.xsl
tool currently behaves differently: In the absence ofCapabilities.NavigationRestrictions/RestrictedProperties/TopSupported
onCapabilities.TopSupported
onThis PR corrects the behavior of the tool. The correction results in additional parameters
in some of the examples.