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
In CQL, you can include a Library in a different namespace (which, loosely, implies a different project):
library Demo
include other.namespace.UltraLibrary as UL
define "Use UL":
UL.X
The cql-language-server should know how to resolve those included libraries if they aren't in the current directory. This may require looking up the correct package on the FHIR package registry and downloading / caching it. It may also require support from the CQL compiler in order to do this correctly. In addition, the cql-language-server needs support for specifying how or where to resolve namespaces from. This is handled in the CQL compiler as the "NamespaceManager." Some namespaces may be able to be auto-detected, while others may require a configuration file in the local project.
The text was updated successfully, but these errors were encountered:
Almost. The namespace corresponds to the root IG url in most cases, which is associated with a package. There needs to be a facility for manually specifying that too, I think.
In CQL, you can include a Library in a different namespace (which, loosely, implies a different project):
The cql-language-server should know how to resolve those included libraries if they aren't in the current directory. This may require looking up the correct package on the FHIR package registry and downloading / caching it. It may also require support from the CQL compiler in order to do this correctly. In addition, the cql-language-server needs support for specifying how or where to resolve namespaces from. This is handled in the CQL compiler as the "NamespaceManager." Some namespaces may be able to be auto-detected, while others may require a configuration file in the local project.
The text was updated successfully, but these errors were encountered: