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
{{ message }}
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.
We noticed in Hops that we can't use environment variables when whitelisting a full object.
Example:
module.exports={foo: {bar: '[FOOBAR]',},browserWhitelist: {foo: true,// does not add `FOOBAR` to the list of environment variables and `foo.bar` will be an empty string.},};
It works though if we use the full path for the entry:
module.exports={foo: {bar: '[FOOBAR]',},browserWhitelist: {'foo.bar': true,// this works as expected},};
Root cause is that we only check for the full path (line 95):
We noticed in Hops that we can't use environment variables when whitelisting a full object.
Example:
It works though if we use the full path for the entry:
Root cause is that we only check for the full path (line 95):
untool/packages/core/lib/utils.js
Lines 92 to 100 in ef7abcc
The text was updated successfully, but these errors were encountered: