-
-
Notifications
You must be signed in to change notification settings - Fork 22
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.
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
Support for Quoted String and Flag #310
Comments
Hi @huanmeng-qwq, thanks for your feedback. The |
I have seen the branches related to quoted strings, and I would like to propose a new suggestion based on #314 , which is to support input of |
I know to add optional parameters to Of course, I also hope to be able to develop complete Flag features as quickly as possible |
GH-310 Relax input restrictions on quoted strings
Now a solution to this problem is |
Yes, I have also considered using escape, which is a great implementation! |
* Add quoted argument resolver. Add related tests. * Fix example command. Add BanCommand to examples. * Fix some suggestions bugs. * Relax input restrictions on quoted strings * Add test * Add more use-cases in unit tests then patch them. --------- Co-authored-by: huanmeng_qwq <1871735932@qq.com>
|
PR:
Issues:
protected
#316I am migrating the framework for command content on a large server project to this project, but I found that it lacks support for Quoted and Flag, and I am not sure if the shortcut annotation supports quick registration of commands with spaces. Here is my examples
/prefix set "§cA §bPrefix"
/tag prefix set "§eB §bPrefix" --updateNow
At the same time, I also hope that Flag annotations are not limited to Boolean, but directly support parsing registered arguments. The following are relevant examples
The text was updated successfully, but these errors were encountered: