Expected behavior
Accessing i18n assets should not pollute the global namespace with lodash.templateSources[]
Actual behavior
Every time you access a page with some i18n results, the template used to render the output leads to an entry added to elements in the source tree in Chrome Console (see screenshot below)
Steps to reproduce behavior
- Open Atlas, and open Chrome console (ctrl-shift-i)
- Navigate around Atlas, especially places containing i18n assets (cohort definition list, etc)
- Observe the following appearing in your
Sources tab of chrome console: a series of lodash.templateSources gets populated, and the volume keeps growing based on the amount of i18n reqeusts (which in some cases is a very intense looping operations that leads to an explosion of nodes:
Expected behavior
Accessing i18n assets should not pollute the global namespace with lodash.templateSources[]
Actual behavior
Every time you access a page with some i18n results, the template used to render the output leads to an entry added to elements in the source tree in Chrome Console (see screenshot below)
Steps to reproduce behavior
Sourcestab of chrome console: a series of lodash.templateSources gets populated, and the volume keeps growing based on the amount of i18n reqeusts (which in some cases is a very intense looping operations that leads to an explosion of nodes: