Open
Conversation
Author
|
I was also thinking about using special syntax in the database field to avoid some complications. So instead of introducing new properties just use e.g. |
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
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.
Search path / Schema #155
Don't seem to be working yet, but I think it should. Can someone give some debug/devel pointers?
I've executed
Extensionlaunch config and was able to debug selecting schema. And also that worked fine :-)But I was not able to debug
src\language\server.ts. Sorry if that is a stupid question, but does the language server need to be executed separately?Also, am I even going in the right direction here? I mean would that kind of feature be OK?