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.

Sign up for GitHub

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

docs: fix typo ("autoCompleteRun" to "autocompleteRun") #249

Merged
merged 1 commit into from
Dec 1, 2023
Merged

docs: fix typo ("autoCompleteRun" to "autocompleteRun") #249

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/Guide/interaction-handlers/autocomplete.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ export class AutocompleteHandler extends InteractionHandler {
## Autocomplete run method

Sapphire will first attempt to find the command class for which the autocomplete is for, and if it exists _and_ it has
the `autoCompleteRun` method set, call it, otherwise we pass it down to interaction handlers. It's the best of both
the `autocompleteRun` method set, call it, otherwise we pass it down to interaction handlers. It's the best of both
worlds, and lets you decide which is better for your projects.

The downside of using `autocompleteRun` is if you have multiple commands that have a similar option and use the same
Expand Down