Sage Abdullah 4bb47f7e25 Move wagtailConfig values to wagtail_config template tag ... The first step on cleaning up our client-side metadata configuration. With this approach, the values are computed in the `wagtail_config` template tag and passed into the template using Django's json_script. Then, it's parsed on the client-side and set as `global.wagtailConfig` to retain compatibility with existing code that rely on `window.wagtailConfig`. This allows us to remove our existing approach of putting metadata values in a `<script>` tag using Django templates directly in the HTML, without changing too much of the existing code, and allowing new code to import the values as `WAGTAIL_CONFIG` from `wagtailConfig.js` instead of using `window.wagtailConfig`. It also means we remove the inline script tag from the core admin base template. Refactor wagtailConfig util - Avoid extraneous named exports when they are included in the named WAGTAIL_CONFIG - Simplify locale map generation - Avoid reading from global, instead export util that can be used as a global - Update unit tests for more robust checks		2024-09-25 14:45:09 -04:00
..
integration
adapter.js
mock-fetch.js
mock-jquery.js
stubs.js	Move wagtailConfig values to wagtail_config template tag	2024-09-25 14:45:09 -04:00
utils.js