fix: Avoid using variable name "module" (#942)
On some configurations variables named `module` may clash with the predefined JS global. resolves #940
This commit is contained in:
parent
882d04c9bf
commit
72427fe2ff
@ -1,6 +1,6 @@
|
||||
import RetrieveMetadata from './services/wado/retrieveMetadata.js';
|
||||
|
||||
const module = 'RetrieveStudyMetadata';
|
||||
const moduleName = 'RetrieveStudyMetadata';
|
||||
// Cache for promises. Prevents unnecessary subsequent calls to the server
|
||||
const StudyMetaDataPromises = new Map();
|
||||
|
||||
@ -17,11 +17,11 @@ export function retrieveStudyMetadata(server, studyInstanceUid) {
|
||||
// corresponding promise from the "StudyMetaDataPromises" map...
|
||||
|
||||
if (!server) {
|
||||
throw new Error(`${module}: Required 'server' parameter not provided.`);
|
||||
throw new Error(`${moduleName}: Required 'server' parameter not provided.`);
|
||||
}
|
||||
if (!studyInstanceUid) {
|
||||
throw new Error(
|
||||
`${module}: Required 'studyInstanceUid' parameter not provided.`
|
||||
`${moduleName}: Required 'studyInstanceUid' parameter not provided.`
|
||||
);
|
||||
}
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user