I'm guessing it's pretty much related to https://github.com/wikimedia/mediawiki-extensions-Wikibase/commit/6e32ab5d3fde0c368831f53f6e81f5c154bf20f7

@Lokal_Profil I believe you're right. This should be configurable. Or am I wrong @daniel?
Isn't there a ticket for this somewhere actually?

This can be closed I guess.

Result maybe be desired in the end but with https://gerrit.wikimedia.org/r/358365 RepoLinker still does not use EntityTitleLookup, so I was not sure if this is now done, or is there still some work left.
If you say it's now all done, then cool!

1. I believe "Statements" header would be needed, unless we really want to make Sense look different than say Forms, or the "top" Lexeme in the regard of how they statements are rendered.

For instance, there might be more than single "Example" statements, translations will be modelled as statements, and there will plenty of other statements involved. Without a header that might be difficult to be rendered in a somewhat reasonable way, I guess.

Thanks!
See also https://gerrit.wikimedia.org/r/358038 for the similar message.

Overall does not seem that horrible, thanks @Ladsgroup

I didn't know what tags should I add, so can you help me with that?

One possible thing to add to the checklist: stop L10n-bot doing updates on github, and make sure it only updates repo on Gerrit. Currently it seems updates are done two boths, which results in both repos diverge more and more :)

With the browser test added this should be done now, right?

@Jan_Dittrich: this is how it would like now, if I try to make it look exactly as form representation (FTR: I am not saying it should look the same, e.g. glosses would most likely in general be longer etc than representation)

All code should be there. Now we have to think about how to deploy this.