You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MADiE export includes the version number in the CQL filename, e.g., Foo-0.0.000.cql
The file contents has library Foo version '0.0.000
The test cases are in tests/measure/Foo , so the folder name matched the CQL library name, Foo.
If that file is opened and Execute CQL is run, it does not look in the Foo folder for the test cases; the output says
"No data found at c:...\input\tests"
If the filename is changed to "Foo.cql" then Execute CQL works with
"Data path: c:...\input\tests\measure\Foo"
It would be nice if Execute CQL could run without changing the CQL filename (keep the filename as exported from MADiE with the version number).
The text was updated successfully, but these errors were encountered:
vscode-cql should be smart enough to find the included libraries whether or not the filename includes the version. If library filename has the version, then vscode-cql can't find the included libraries and causes a lot of CQL errors.
MADiE export includes the version number in the CQL filename, e.g., Foo-0.0.000.cql
The file contents has
library Foo version '0.0.000
The test cases are in tests/measure/Foo , so the folder name matched the CQL library name, Foo.
If that file is opened and
Execute CQL
is run, it does not look in the Foo folder for the test cases; the output says"No data found at c:...\input\tests"
If the filename is changed to "Foo.cql" then
Execute CQL
works with"Data path: c:...\input\tests\measure\Foo"
It would be nice if
Execute CQL
could run without changing the CQL filename (keep the filename as exported from MADiE with the version number).The text was updated successfully, but these errors were encountered: