Implement basic command flag suggestion filter #1304
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Pugzy <[email protected]>
Pablete1234
requested changes
Mar 3, 2024
Signed-off-by: Pugzy <[email protected]>
Pablete1234
approved these changes
Mar 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our current no-filter approach suggests command flags first (and incorrectly) instead of partly formed inputs.
Currently running
/ban den[tab]changes the input to/ban --silentand then/ban --time.This change means that command flags will only be suggested if:
-/--The above
bancommand example is from Community which extends the PGM command graph, to see an example baked in to PGM the/setnextcommand can be used which has--forceand--resetflags.