`search` command name keyword is not case-insensitive as stated in documentation
Opened this issue · 1 comments
conradsoon commented
nus-se-script commented
Team's Response
Documentation bug. It is intended to be case sensitive matching in v1.4.
This issue was fixed in a later PR but could not be pulled due to feature freeze.
Items for the Tester to Verify
❓ Issue response
Team chose [response.NotInScope
]
- I disagree
Reason for disagreement: [replace this with your explanation]
❓ Issue type
Team chose [type.DocumentationBug
]
Originally [type.FunctionalityBug
]
- I disagree
Reason for disagreement: [replace this with your explanation]