This repository has been archived by the owner on Jun 11, 2021. It is now read-only.
feat(core): process completion as a state enhancer #29
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This removes the top-level
getCompletion()API and enhance the autocomplete state with acompletionproperty.Conceptually, it makes more sense for the completion to be in the state rather than available in a separate method. It also makes possible to leverage it in the sources and templates now.
I'm thinking of using this "state enhancer" patterns to support plugins. I'll experiment with a plugin API and try to introduce
autocomplete-plugin-recent-searchesbased on this concept.