Remove legacy autocompletion with Kibana spec - #219
Merged
Conversation
pquentin
commented
Jan 20, 2026
Collaborator
Author
There was a problem hiding this comment.
I initially wanted to keep parts of this, but tests/test_schema_completer.py covers everything that is not Kibana-specific.
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
2 participants
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.
Since peek is still in its 0.x phase and Kibana spec supported was deprecated two years ago, it seemed fine to simply drop it, but I can add code to recognize
prefer_elasticsearch_specification = Falseand raise an error in this case.