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
Packaging the existing process.env configuration into a ProcessEnvConfigService and putting an interface.js abstraction layer around it.
Create an ImportConfigService (or a better name) which imports configuration from 'env.config', as expected in frontend-build.
Determine the right rollout strategy which enables backwards compatibility with the existing process.env-based configuration, while allowing MFEs to opt into the JS-based configuration.
The content you are editing has changed. Please copy your edits and refresh the page.
@davidjoy is this open for the community to own? or is it something edx is already working on internally?
I ask because I am interested in working on it (given also this has been brought up in the last FEWG #49)
https://github.com/edx/frontend-platform needs to be updated to allow for JS-based configuration.
This should look something like:
process.env
configuration into aProcessEnvConfigService
and putting aninterface.js
abstraction layer around it.ImportConfigService
(or a better name) which imports configuration from'env.config'
, as expected in frontend-build.PRs
The text was updated successfully, but these errors were encountered: