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
Just as an idea, if multiple packages inject stuff into the app there are multiple script tags. Alone my translator package injects 2 things and because of that there are 2 script tags.
This also pollutes the global id namespace.
<scriptid='translator-namespaces' type='application/ejson'>{"both/l10n/public":{"de_DE":1,"en_US":1}}</script><scriptid='translator-language' type='application/ejson'>{"$type":"Translator.LanguageArray","$value":"de_DE de en_US en"}</script>
I just thought if it would be possible to combine all object injects into one with an id that is long enough to not interfere with other id's.
<scriptid='inject-initial' type='application/ejson'>{"translator-namespaces":{"both/l10n/public":{"de_DE":1,"en_US":1}},"translator-language":{"$type":"Translator.LanguageArray","$value":"de_DE de en_US en"}}</script>
The text was updated successfully, but these errors were encountered:
Yeah, it could be nice to save on the bytes for cases where multiple / different packages are all using it. I do think though that it's quite nice to so clearly see where all the data comes from, but I guess in production the speed is more important. So yes, this is definitely something we can consider.
Just as an idea, if multiple packages inject stuff into the app there are multiple script tags. Alone my translator package injects 2 things and because of that there are 2 script tags.
This also pollutes the global id namespace.
I just thought if it would be possible to combine all object injects into one with an id that is long enough to not interfere with other id's.
The text was updated successfully, but these errors were encountered: