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
An app's config has always been included as a meta tag in the app's index.html file (unless you set storeConfigInMeta to false, then the actual config object is included inside the config module).
Since v1.0.0 of this addon, an app's config is now also included in vendor.js.
Since v1.0.3 of this addon, an app's test config is now also included in vendor.js (even for production builds).
I don't feel this is the right direction to take.
I think the focus should be more on resolving the app's config at runtime as mentioned in the beginning of this addon's README.
If I'm not mistaken, this also breaks the flow for companies who build their app once and then create different configured versions of their app by replacing the meta tag in index.html.
The text was updated successfully, but these errors were encountered:
An app's config has always been included as a
meta
tag in the app'sindex.html
file (unless you setstoreConfigInMeta
tofalse
, then the actual config object is included inside the config module).Since v1.0.0 of this addon, an app's config is now also included in
vendor.js
.Since v1.0.3 of this addon, an app's test config is now also included in
vendor.js
(even for production builds).I don't feel this is the right direction to take.
I think the focus should be more on resolving the app's config at runtime as mentioned in the beginning of this addon's README.
If I'm not mistaken, this also breaks the flow for companies who build their app once and then create different configured versions of their app by replacing the
meta
tag inindex.html
.The text was updated successfully, but these errors were encountered: