We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If someone provides a prompt like:
new cars are safer than old cars right?
or
session tracking in php is easy, right?
It's going to accidentally be triggering the new command, and the session command.
new
session
But what's the solution? Do we make all commands require a fore slash or something? new becomes /new?
/new
Does anyone have an opinion, is it worth changing?
The text was updated successfully, but these errors were encountered:
If you're seeking opinions, mine would be to prepend with a slash. Ambiguity bad
Sorry, something went wrong.
I also agree with requiring slashes
implemented long ago, command leader is forward slash now.
No branches or pull requests
If someone provides a prompt like:
new cars are safer than old cars right?
or
session tracking in php is easy, right?
It's going to accidentally be triggering the
new
command, and thesession
command.But what's the solution? Do we make all commands require a fore slash or something?
new
becomes/new
?Does anyone have an opinion, is it worth changing?
The text was updated successfully, but these errors were encountered: