Fix metta completion #7
Merged
+30
−17
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
doc_text/2 doesn't seem to be used anywhere else; without this, various other predicates use lsp_state:full_text/2 and lsp_state:full_text_next/2 (both? I am somewhat unclear what the difference is) and so don't see unsaved updates to files
Previously this was trying to use the prolog xref to look up metta definitions which obviously isn't going to do anything terrible helpful.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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.
Making some changes to make the code completion in metta files give results. Previously it wasn't working because both the change tracking had bit-rotted slightly between implementations and looking up candidate symbols was still using the prolog xref rather than metta.