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:
Ivan Aksamentov 2019-09-23 15:05:26 +02:00 committed by Erik Ziegler
parent 882d04c9bf
commit 72427fe2ff

View File

@ -1,6 +1,6 @@
import RetrieveMetadata from './services/wado/retrieveMetadata.js'; import RetrieveMetadata from './services/wado/retrieveMetadata.js';
const module = 'RetrieveStudyMetadata'; const moduleName = 'RetrieveStudyMetadata';
// Cache for promises. Prevents unnecessary subsequent calls to the server // Cache for promises. Prevents unnecessary subsequent calls to the server
const StudyMetaDataPromises = new Map(); const StudyMetaDataPromises = new Map();
@ -17,11 +17,11 @@ export function retrieveStudyMetadata(server, studyInstanceUid) {
// corresponding promise from the "StudyMetaDataPromises" map... // corresponding promise from the "StudyMetaDataPromises" map...
if (!server) { if (!server) {
throw new Error(`${module}: Required 'server' parameter not provided.`); throw new Error(`${moduleName}: Required 'server' parameter not provided.`);
} }
if (!studyInstanceUid) { if (!studyInstanceUid) {
throw new Error( throw new Error(
`${module}: Required 'studyInstanceUid' parameter not provided.` `${moduleName}: Required 'studyInstanceUid' parameter not provided.`
); );
} }