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
First up, thanks for the great tool. It's saved me so much time over the years!
Problem
I need to see how my application is configured in production or other environments. This configuration information is stored in an URL encoded format in one or more <meta> tags in the <header> of my app. This config is not easily readable by humans in it's stored format.
Solution
Add an application configuration section. This could be added to the info section.
Details
The config for the current (3.17.0-beta.1) default output of ember-cli looks like this:
Not fun to read. It can be easily parsed by copying the contents and pasting them into JSON.parse(decodeURIComponent('encoded content here')), but this requires knowledge of the special command and is a bit cumbersome.
The text was updated successfully, but these errors were encountered:
This seems like a great feature to me. However I think there are a few possible ways for an app to ship the config other than through the <meta> tag. @rwjblue do you happen to know if there is a single way (e.g. requiring a well know module path?) to get it reliably?
Ya, you can require('app-name/config/environment') to get it. When using the <meta> that module is doing document.querySelector to read the value and parse it, when using storeConfigInMeta: false that module is literally the JS value you want.
First up, thanks for the great tool. It's saved me so much time over the years!
Problem
I need to see how my application is configured in production or other environments. This configuration information is stored in an URL encoded format in one or more
<meta>
tags in the<header>
of my app. This config is not easily readable by humans in it's stored format.Solution
Add an application configuration section. This could be added to the info section.
Details
The config for the current (3.17.0-beta.1) default output of ember-cli looks like this:
Not fun to read. It can be easily parsed by copying the contents and pasting them into
JSON.parse(decodeURIComponent('encoded content here'))
, but this requires knowledge of the special command and is a bit cumbersome.The text was updated successfully, but these errors were encountered: