-
Notifications
You must be signed in to change notification settings - Fork 476
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
$select = complexProperty/complexColProperty query option is not support #196
Comments
Is there an ETA for supporting this yet? Going on two and a half years now, and it's still needed. Maybe @robward-ms can re-assign it to someone else? Thanks! |
@robward-ms Any news on this feature? |
No news here; the team is focused on getting WebApi AspNetCore finished up before tackling new features. |
This issue affects Azure Search as well. We are expanding the semantics of $select in our API to handle complex types. I investigated this issue to the point where I have a sense of the scope of the fix, and it's not small. I already have a workaround in place, so unfortunately it's not worth the effort for my team to take this on. However, I did write an E2E test that will be useful for the next person who tackles this. That was surprisingly difficult too due to some EF dependencies in the E2E tests. I'll send a PR for that shortly. |
In the spirit of TDD, I wrote a failing test before attempting to fix this issue: OData#196 Unfortunately, the fix looks more like a large and complex feature than just a simple bug fix, and I don't have bandwidth to take it on right now. However, the test may still be useful for the next person to make the attempt.
In the spirit of TDD, I wrote a failing test before attempting to fix this issue: #196 Unfortunately, the fix looks more like a large and complex feature than just a simple bug fix, and I don't have bandwidth to take it on right now. However, the test may still be useful for the next person to make the attempt.
@robward-ms, @xuzhg is there any news on this feature? |
@mikepizzo @xuzhg Any idea on when we can expect to get this feature? |
@robward-ms, @xuzhg is there any news on this feature? |
@suadev Thanks for querying. I am busy on this feature now. I hope I can finish it quickly and release it in the next version. |
@xuzhg - We're extending our Api to support Complex Properties and getting the same error during serialization. Kindly let me know if the fix that you're implementing is part of System.Web.OData v5.x and when can we expect the fix to be released Version of System.Web.Odata being used - 5.9.0 |
@VenuMadhavPerumalla Thanks for letting us know your scenarios. Unfortunately, We are focus on 7.x version and 5.x is in maintenance status. |
It block me to use ef core owned type, any workaround for this ? |
@keatkeat87 Thanks for querying this. I just created a PR to enable it. Hope i can finish it as soon as possible if the code review works well. |
@xuzhg any news for your PR? |
My PR got merged. It's released in 7.2.3 |
query like ?$select=Address/Line1,Address/Line2,Address/PostCode is not support
In System.Web.OData.Formatter.Serialization.SelectExpandNode
ValidatePathIsSupported function :
when segmentCount == 2, only support first segment is a Type Segment, only support paths of type 'cast/structuralOrNavPropertyOrAction'
The text was updated successfully, but these errors were encountered: