@Lucas_Werkmeister_WMDE, do you have something to comment? Thank you.

Change #1231682 had a related patch set uploaded (by IKhitron; author: IKhitron):

[mediawiki/extensions/GlobalWatchlist@master] Add support for EntitySchema pages in Global Watchlist

https://gerrit.wikimedia.org/r/1231682

wbsearchentities (not wbgetsearchentities) isn’t really the right API for this, but there isn’t another API either – EntitySchema has very poor API support, as a result of our decision years ago to not base it on Wikibase. I guess it’s possible to implement GlobalWatchlist support this way, yes.

Alternatively, GlobalWatchlist could have some sort of hook or extensibility mechanism that allows an extension, such as EntitySchema, to customize it, and then it would be EntitySchema’s responsibility to figure out how to display the page title properly. (This would be fairly straightforward in PHP; but given that IIUC this all happens in JS, EntitySchema itself would still need some kind of API to access the labels. But at least it would be encapsulated within that extension.)

In T415450#11553296, @Lucas_Werkmeister_WMDE wrote:

wbsearchentities (not wbgetsearchentities) isn’t really the right API for this, but there isn’t another API either – EntitySchema has very poor API support, as a result of our decision years ago to not base it on Wikibase. I guess it’s possible to implement GlobalWatchlist support this way, yes.

Alternatively, GlobalWatchlist could have some sort of hook or extensibility mechanism that allows an extension, such as EntitySchema, to customize it, and then it would be EntitySchema’s responsibility to figure out how to display the page title properly. (This would be fairly straightforward in PHP; but given that IIUC this all happens in JS, EntitySchema itself would still need some kind of API to access the labels. But at least it would be encapsulated within that extension.)

Thank you for the answer. Sorry for the typo. About API - I'm not going to create a bottleneck. What I'm building is, conceptually, E35<span class="entityschemawaiting" data-label="E35"></span> shown to the user and running a function to get the API data and add the span text asynchronously, after the GlobalWatchlist refresh is ready. All this with caching, as I already mentioned, allowing to show older results immediately and reducing the number of API calls as much as possible. @Tacsipacsi recommends against preferences usage, so I'm considering local storage.

About the delegation, if it will happen from the EntitySchema side, it will be great, but I can't order them do it, of course, so I can just implement in on this side and be ready to change later.

@Lucas_Werkmeister_WMDE, could you tell me, please, if the fact that Lexemes labels do not get language fallback is a bug or a feature? Thank you.
And btw, why wbsearchentities ignores all the language parameters? The call https://www.wikidata.org/w/api.php?action=wbsearchentities&format=json&search=E1&language=es&strictlanguage=1&type=entity-schema&formatversion=2, and another without the strictlanguage flag, return both the English results, while the Spanish do exist for this page.

In T415450#11571500, @IKhitron wrote:

@Lucas_Werkmeister_WMDE, could you tell me, please, if the fact that Lexemes labels do not get language fallback is a bug or a feature? Thank you.

Lexemes don’t have labels, they have lemmas. When displaying lexemes, all lemmas should be shown at once (example), so language fallback doesn’t really apply.

And btw, why wbsearchentities ignores all the language parameters? The call https://www.wikidata.org/w/api.php?action=wbsearchentities&format=json&search=E1&language=es&strictlanguage=1&type=entity-schema&formatversion=2, and another without the strictlanguage flag, return both the English results, while the Spanish do exist for this page.

language= controls the language of the search input, uselang= controls the language of the result output. You probably want to set both of them (language= doesn’t really matter if you’re searching for an entity ID, but it’s a required parameter so you can’t omit it either); strictlanguage= shouldn’t matter when searching for an entity ID.

In T415450#11573267, @Lucas_Werkmeister_WMDE wrote:

In T415450#11571500, @IKhitron wrote:

@Lucas_Werkmeister_WMDE, could you tell me, please, if the fact that Lexemes labels do not get language fallback is a bug or a feature? Thank you.

Lexemes don’t have labels, they have lemmas. When displaying lexemes, all lemmas should be shown at once (example), so language fallback doesn’t really apply.

So, it's a feature. Thanks a lot.

And btw, why wbsearchentities ignores all the language parameters? The call https://www.wikidata.org/w/api.php?action=wbsearchentities&format=json&search=E1&language=es&strictlanguage=1&type=entity-schema&formatversion=2, and another without the strictlanguage flag, return both the English results, while the Spanish do exist for this page.

language= controls the language of the search input, uselang= controls the language of the result output. You probably want to set both of them (language= doesn’t really matter if you’re searching for an entity ID, but it’s a required parameter so you can’t omit it either); strictlanguage= shouldn’t matter when searching for an entity ID.

I see. Great, I can fix it now. Thanks a lot for your help.