The depth limit for entries in nested expanded navigation links was reached - AspNetCore.OData 9.0 #1314
Comments
|
Hi @KryptoBeard. Thank you for reaching out to us. How does it behave when there's no |
The exact same. Without it throws the same error, I add the max expansion depth property, same error. |
|
@KryptoBeard can you share how your controller action method signature looks like? |
|
Sure thing. [HttpGet, EnableQuery(MaxExpansionDepth = 5)]
[Authorize(PatientPrivileges.Read)]
public IActionResult Get(Guid key)
{
return Ok(SingleResult.Create(_odataPatient.GetQueryableWithSpec(new PatientByIdSpec(key))));
}Which is just returning Query.Where(f=>f.Id == key) IQueryable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Assemblies affected
Microsoft.AspNetCore.OData 9.0
Describe the bug
I do not run into this issue on OData 8.x, when upgrading I get this - Even when having MaxExpansionDepth = 5 or even 0 on the EnableQuery Attribute.
The depth limit for entries in nested expanded navigation links was reached. The number of nested expanded entries cannot exceed 2.
Reproduce steps
Create a Get Endpoint that has a a large amount of nested expands. It doesn't seem like the MaxExpansionDepth Property on the EnableQuery attribute is working correctly?
Request/Response
Please share your request Uri, head or the request body
Please share your response head, body.
Returns nothing , a blank body with a 200 response - and throws this error.
The depth limit for entries in nested expanded navigation links was reached. The number of nested expanded entries cannot exceed 2.
Expected behavior
A clear and concise description of what you expected to happen.
It should return a 200 response with the expanded properties like it does in OData 8.x
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Please share your call stack or any error message
The text was updated successfully, but these errors were encountered: