-
Notifications
You must be signed in to change notification settings - Fork 23
fix(externalRegistry): prevent undefined entries #150
Conversation
* @param {string} externals.[externalName].semanticRange semantic range module will accept | ||
* @param {string} externals.[externalName].integrity hash value of fallback external | ||
*/ | ||
function setModulesRequiredExternals({ moduleName, externals = {} }) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If externals are undefined, should we be setting anything at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i thought the same, landed on if a moduleName is provided it would be expected to be entered into the registry. Im not 100% tied to this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But if no externals are being passed, then the module technically doesn't require any externals at that point in time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which is why i think it could be empty.
Co-authored-by: Matthew Mallimo <matthew.c.mallimo@aexp.com>
Description
Limits the chance of external registries from having
undefined
entriesAlso included JSdoc declarations for external registry
Motivation and Context
fixes bug when integrated with One App.
How Has This Been Tested?
unit tests, tested locally by installing in to one-app server and running one-apps integration test suite. integration tests failed before changes and succeed after.
Types of Changes
Checklist:
What is the Impact to Developers Using Holocron?