Skip to content
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

Suggest corrections for badly read part codes #20

Open
PeterJCLaw opened this issue May 5, 2019 · 0 comments
Open

Suggest corrections for badly read part codes #20

PeterJCLaw opened this issue May 5, 2019 · 0 comments

Comments

@PeterJCLaw
Copy link
Member

The inventory has a limited list of characters which are used in part codes. For example: while 0 is a valid part code character, neither o nor O are.
Currently the tooling outright rejects bad characters, however it should be fairly easy to detect the presence of these characters and provide a clearer message to the user.

Follow-on steps from this might be:

  • also checking whether a part code exists with the "corrected" name
  • just redirecting the query/operation onwards with the "corrected" name

The latter in particularly needs deeper consideration as it trains users that these invalid characters are in fact valid, which would likely lead to them not writing part codes clearly in their proper form and/or not being aware of the intentionally limited alphabet at all. Both of these could cause considerable confusion when the tooling refers to one spelling but users are expecting another.

This task therefore is explicitly only about improving the messaging to users and not about changing the current behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant