Improve error messages for partial/ambiguous commands

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
cli, game-dev

Research direction

Start at the parser behavior that returns CommandType.Unknown for unrecognized input. Define how misspelled directions, partial item names, and commands missing targets should produce contextual hints, using the examples in the issue as acceptance cases; done means each case gives a useful suggestion instead of only Unknown.

Written by the indexing model from the issue text.

Description

engine enhancement squad:banner

The parser currently returns CommandType.Unknown for anything it doesn't recognize. Improve UX: suggest closest match for misspelled directions (e.g. 'go nroth' -> 'Did you mean north?'), handle partial item names better, give contextual hints when a command is missing its target.

Dominant language
C#
Stars
1
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from csharpfritz/MyFirstTextGame

All issues in csharpfritz/MyFirstTextGame

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.