Store backend command tree per server connection to allow on-demand resending of command set#865
Merged
Merged
Conversation
…esending of command set
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Statefully stores the backend's command tree, so we can send & inject our own commands at a later time.
Functionally this PR does nothing right now, however this is needed to suppress the sending of the
/velocity:callbackcommand to the client when no callbacks are registered. With no plugin making use of adventure's click-callback feature, no callbacks will ever be registered, so we can avoid sending this to the client completely. This avoids the ugly auto-complete.