Trigger a type check for an entire Rascal project from VS Code#1153
Trigger a type check for an entire Rascal project from VS Code#1153rodinaarssen wants to merge 34 commits into
Conversation
DavyLandman
left a comment
There was a problem hiding this comment.
Very nice! I have some small remarks. But the most important one is that I'm missing a UI test for this feature.
| <dependencyMsgs, checkedForImports, dependencies> = buildDependencyGraph(checkForImports, openFileHeader.src, workspaceFolders, getParseTree, getPathConfig); | ||
|
|
||
| if ([] != dependencyMsgs) { | ||
| // Since we only reported errors on `l`, there is not need to analyze to which files the errors belong here. |
There was a problem hiding this comment.
how is this true? can't we have error from our dependencies?
There was a problem hiding this comment.
This is the "check-on-save" path, where errors have never been reported on dependencies, but on the file itself
toinehartman
left a comment
There was a problem hiding this comment.
Nice feature! Looks good. I don't love the additional document service endpoint, since it's only for Rascal (and does not mean anything for parametric or the to-be-added routing server).
84cde51 to
943a6d7
Compare
943a6d7 to
fb5e1d0
Compare
|



This PR adds:
This PR may depend on a release of Rascal that contains usethesource/rascal#2815