Framework: include file with default config values #1128
Labels
Framework
[Status] Stale
[Type] Enhancement
Changes to an existing feature — removing, adding, or changing parts of it
We have few config values, which are the same in all environments:
Some of them are long and copy/testing seems tedious and error-prone. Also, adding a new config key often means adding it to all configs, which is slightly annoying.
Do you think this is a problem? If yes, what’s the best solution?
My first reaction is to have a
common.json
, which is loaded in all environments.I'd like to rework how we handle the configs so that we can build a single bundle and then process that bundle to remove dead code and minify when creating the builds for
production
andstage
. This would removeclient/config/regenerate.js
and simplify the build process.The text was updated successfully, but these errors were encountered: