Relints documents when connecting / disconnecting to a database #318
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.
The failing behaviour can be seen in the test added by 706f9ec.
Why
Because if we ask to lint a document when the schema is yet not fetched, we will never see schema dependent errors (non existent labels, deprecation warnings, non existent procedures, etc). This can happen when we open the the editor open with a cypher file when we haven't yet connected to a database.
Conversely, when we disconnect from a database, this should also relint the document.
This will become more relevant when we have several connections and we can be connected to different databases with different procedures / functions, different labels, ...