| • Jonas | |
| May 17 2017, 1:15 PM |
| F22663938: Bildschirmfoto von 2018-06-26 10-06-28.png | |
| Jun 26 2018, 8:15 AM |
| F22663998: Bildschirmfoto von 2018-06-26 10-09-33.png | |
| Jun 26 2018, 8:15 AM |
| F22663999: Bildschirmfoto von 2018-06-26 10-09-43.png | |
| Jun 26 2018, 8:15 AM |
| F8110369: image.png | |
| May 17 2017, 1:15 PM |
| F8110376: image.png | |
| May 17 2017, 1:15 PM |
When selecting an Item it is not possible to choose the right one, because the description is missing
VS.
Also there are questions for consistency:
Consider moving the resulting component to wikibase to make usable from other product (e.g. mediainfo).
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Show description in the item selector on Special:NewLexeme | mediawiki/extensions/WikibaseLexeme | master | +165 -12 |
My first thought is that we want to be as consistent with the item selector on item pages as possible.
Change 441555 had a related patch set uploaded (by Jakob; owner: Jakob):
[mediawiki/extensions/WikibaseLexeme@master] Show description in the item selector on Special:NewLexeme
What was the decision on showing the id generally? Answered by "as consistent with the item selector on item pages as possible"? EntitySelector in lexeme header does show the id after the label.
No label and description properties on data in getLookupMenuOptionsFromData() if not present in item - provide a fallback to id, maybe? Admittedly a strange situation but happened to be the case in my dev.
If an list item with existing label and description is selected the newly created HTML - in escaped fashion - is used as input value (UI-wise not technically).
Change 441555 merged by jenkins-bot:
[mediawiki/extensions/WikibaseLexeme@master] Show description in the item selector on Special:NewLexeme