StackExchange / StackExchange/StackExchange.Redis
Suggestion: unknown command - respond with enhanced metadata in exception
Open
Nobody has claimed this yet.
⚙️ area:logging
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
For example, someone tries to run HSETEX on a v6 server; we could have the library report that this is a server 8.0 feature, in a single consistent unified location.
Notes:
- do not change
.Message- just the.ToString(), so that existing consumers are not adversely impacted
Contributor guide
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; start by locating the exception path used for unknown Redis commands and its existing ToString() coverage. Use the HSETEX-on-a-v6-server example to determine where server feature metadata belongs, while preserving Message and showing the enhanced information only through ToString().
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100