-
Notifications
You must be signed in to change notification settings - Fork 64
Closed
Labels
priority:p1High priority but not blocking. Causes major but not critical loss of functionality SLA <=7daysHigh priority but not blocking. Causes major but not critical loss of functionality SLA <=7days
Description
Follow up to #232
Related to microsoftgraph/msgraph-metadata#449
Setting ContainsTarget="false" on a navigation property prevents the enabling of a function/action on nav property due to the check below preventing the generation of the path because it doesn't allow for the evaluation of the ExplicitBinding annotation.
| if (!npSegment.NavigationProperty.ContainsTarget) |
Given the original intention of #232, the generation of a path when contains ContainsTarget="false" should take into consideration that nav property has the explicit operation binding.
In summary, we should have the following scenarios,
| Scenario | ContainsTarget | ExplicitBinding present | Generate? |
|---|---|---|---|
| 1 | False | False | NO |
| 2 | False | True | YES (missing scenario) |
| 3 | True | False | YES (already works, as the containsTarget allows this ) |
| 4 | True | True | YES (already works, as the containsTarget allows this) |
This blocks adding paths to nav properties where contains target is false as seen in microsoftgraph/msgraph-metadata#449
Metadata
Metadata
Assignees
Labels
priority:p1High priority but not blocking. Causes major but not critical loss of functionality SLA <=7daysHigh priority but not blocking. Causes major but not critical loss of functionality SLA <=7days