Change Details

**Motivation** Config value mw.config.get( 'wbEntity' ) has been deprecated two years ago and on large items this is horrendously wasteful and will slow down client side rendering/page load time. Germany for instance the HTML has a page size of 2.9MB which is unacceptably big (removing the config property drops the page size down to 2MB). **Problem** In the code, it still loads the value, when firing the hook (wbEntity is deprecated in favor of wikibase.entityPage.entityLoaded hook) **Suggested Solution / Technical Details** Replace the firing hook with an API call for now to make it asynchronous and drop serving the config value entirely. --- **Original bug report:** I noticed when exploring the config values on Wikidata the config value mw.config.get( 'wbEntity' ) On large items this is horrendously wasteful and will slow down client side rendering/page load time. Germany for instance the HTML has a page size of 2.9MB which is unacceptably big (removing the config property drops the page size down to 2MB). I am sure this data can be sent to the client in better ways. I doubt many of the values are used by anything and some would be better as data attributes on the HTML itself. Grepping the code base nothing seems to be currently using it (but I assume some gadgets might be)/ I'd thus recommend killing its use asap.

**Motivation** Config value mw.config.get( 'wbEntity' ) has been deprecated two years ago and on large items this is horrendously wasteful and will slow down client side rendering/page load time. Germany for instance the HTML has a page size of 2.9MB which is unacceptably big (removing the config property drops the page size down to 2MB). **Problem** In the code, it still loads the value, when firing the hook (wbEntity is deprecated in favor of wikibase.entityPage.entityLoaded hook) **Suggested Solution / Technical Details** Replace the firing hook with an API call for now to make it asynchronous and drop serving the config value entirely. * Deprecation has been announced previously * We have to announce this as per BC process --- **Original bug report:** I noticed when exploring the config values on Wikidata the config value mw.config.get( 'wbEntity' ) On large items this is horrendously wasteful and will slow down client side rendering/page load time. Germany for instance the HTML has a page size of 2.9MB which is unacceptably big (removing the config property drops the page size down to 2MB). I am sure this data can be sent to the client in better ways. I doubt many of the values are used by anything and some would be better as data attributes on the HTML itself. Grepping the code base nothing seems to be currently using it (but I assume some gadgets might be)/ I'd thus recommend killing its use asap.

**Motivation** Config value mw.config.get( 'wbEntity' ) has been deprecated two years ago and on large items this is horrendously wasteful and will slow down client side rendering/page load time. Germany for instance the HTML has a page size of 2.9MB which is unacceptably big (removing the config property drops the page size down to 2MB). **Problem** In the code, it still loads the value, when firing the hook (wbEntity is deprecated in favor of wikibase.entityPage.entityLoaded hook) **Suggested Solution / Technical Details** Replace the firing hook with an API call for now to make it asynchronous and drop serving the config value entirely. * Deprecation has been announced previously * We have to announce this as per BC process --- **Original bug report:** I noticed when exploring the config values on Wikidata the config value mw.config.get( 'wbEntity' ) On large items this is horrendously wasteful and will slow down client side rendering/page load time. Germany for instance the HTML has a page size of 2.9MB which is unacceptably big (removing the config property drops the page size down to 2MB). I am sure this data can be sent to the client in better ways. I doubt many of the values are used by anything and some would be better as data attributes on the HTML itself. Grepping the code base nothing seems to be currently using it (but I assume some gadgets might be)/ I'd thus recommend killing its use asap.