-
Notifications
You must be signed in to change notification settings - Fork 9.5k
core(config): use fr config to construct the legacy config #13965
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
maybe that should happen in one PR? Presumably that would preserve more blame since a lot of things (like UIStrings) would be unchanged |
Hmm yeah, also looks like the id for all the UI strings gets updated so I will try that. |
This reverts commit da5ddbc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
In a follow-up PR I am planning to remove the fraggle-rock/ config folder and replace it with a legacy one.
Should do this first: #14105
Previously the fr default config was just the legacy default config with a few modifications. This PR just reverses the relationship so the new default will be all in one file. The FR config now lives in
default-config.js
and the legacy config lives inlegacy-default-config.js
.In a follow-up PR I am planning to remove the
fraggle-rock/
config folder and replace it with alegacy
one.