Allows custom plugins to pop up during completion with standalone projects #251
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
nkakouros
force-pushed
the
standalone-plugins
branch
from
1bf433a
to
c93eee0
Compare
nkakouros
force-pushed
the
standalone-plugins
branch
from
c93eee0
to
d91b75e
Compare
nkakouros
changed the title
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.
contribution under the same terms as this project's license, and
that I have the right to license my contribution under those terms.
cc: @mbland
When setting
_GO_STANDALONE, custom plugins are not returned with tab completion. This is counter-intuitive IMHO. Plugins are super convenient to organize code and share it among projects. There is no reason really for such custom code to not be returned as suggested commands to the user, since the purpose of that custom code is 99.9% to be used by the user.