Appending f/ does not ignore the warning.

[jeremiahlzz]

Appending f/ directly does not clear warnings as documented in the error message.

Adding a space before /f is required.

[nus-se-bot]

Team's Response

UG states the f/ prefix to have a space:

I believe that it should be naturally understood that f/ should be treated as any other prefix and have a space before them. Similarly, the normal/universal definition of append isn't a strict adding to the end without any space, but a general statement of attaching the prefix to the end (see below image example).

That having said, the error message has rooms for improvement: append " f/" to ignore the warning or add the f/ flag to ignore the warning (in the latter case the user would lookup the user guide to see how the flag is used). So valid feature request.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: As said by the team, an easy fix is changing the error message to add prefix f/ to ignore the warning or add the f/ flag to ignore the warning.

Easily done and is important to users when they encounter an error and could potentially cause frustration.

---