Skip to content

Enable Client Completions for non-Sponge/Brig commands. #3107

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

Merged
merged 3 commits into from
Aug 7, 2020

Conversation

dualspiral
Copy link
Contributor

@dualspiral dualspiral commented Aug 1, 2020

SpongeAPI | SpongeCommon

  • Split raw commands from the parameterized commands registrar completely to support this change
  • Fix /sponge which not working with namespaced commands

This should be the last major change for commands, I think this is the last thing that needed doing.

There is a lot going on here but most of this is for enabling client completions for non-Sponge and non-Brig commands, as well as fixing a few issues. Command tab completion now works for non-Sponge commands, the way that third parties tell Sponge about the structure of their commands is now a little saner.

Also, /sponge which now works properly as I treat the commands are resource keys on the client - fixing namespaced commands coming up red.

I also moved the commands from the test plugin into its own plugin.

* Split raw commands from the parameterized commands registrar completely to support this change
* Fix /sponge which not working with namespaced commands
@dualspiral dualspiral force-pushed the api8/clientcompletion branch from c8e87e6 to e319aa1 Compare August 7, 2020 09:57
@dualspiral dualspiral merged commit 0a580cb into api-8 Aug 7, 2020
@dualspiral dualspiral deleted the api8/clientcompletion branch August 7, 2020 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant