Skip to content

Order value should pass to selector model generated #986

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

Closed
xuzhg opened this issue Jul 12, 2023 · 0 comments · Fixed by #1005
Closed

Order value should pass to selector model generated #986

xuzhg opened this issue Jul 12, 2023 · 0 comments · Fixed by #1005
Labels
bug Something isn't working

Comments

@xuzhg
Copy link
Member

xuzhg commented Jul 12, 2023

Assemblies affected
Which assemblies and versions are known to be affected e.g. ASP.NET Core OData 8.x

Describe the bug
A clear and concise description of what the bug is.

Reproduce steps

Supposed customers set up the order value on the attribute, after OData attribute routing convention, this order value is gone.

 [Route("/Data(Key1={Key1}, Key2={Key2})", Order = -1)]
 public IActionResult GetOne(long Key1, string Key2)
{
   ..
}

We should pass the order value into the new selector model generated in the OData attribute routing convention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant