We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
fixes #986: pass Order value to selector model generated
4472f7b
8569df8
fixes #986: add Order for conventional, fixes the failing test, updat…
32b9b0a
…e the sample
Successfully merging a pull request may close this issue.
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.
We should pass the order value into the new selector model generated in the OData attribute routing convention.
The text was updated successfully, but these errors were encountered: