Error message for not allowed queryoptions should not contain information on how to enable it.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 505
- Forks
- 186
- PR merge metrics
- No merged PRs in 30d
Description
Assemblies affected
ASP.NET Core OData 8.0.11
Describe the bug
When disabling QueryOptions, for example by setting AllowedQueryOptions = AllowedQueryOptions.None, the error message now adds the following to the error message: "To allow it, set the 'AllowedQueryOptions' property on EnableQueryAttribute or QueryValidationSettings."
Since this error is (by default) send to the client, it doesn't make sense to add this message and thus should be removed. The client is not able to enable these features.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by locating the error-message construction for disabled QueryOptions and confirm how the message is returned to clients. Done means the guidance about enabling QueryOptions is absent from that client-facing error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100