Last modified: 2013-08-31 09:41:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43558, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41558 - wikibase API should accept upper-case ID prefixes
wikibase API should accept upper-case ID prefixes
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
WikidataRepo (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Wikidata bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-30 16:12 UTC by Daniel Kinzler
Modified: 2013-08-31 09:41 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Daniel Kinzler 2012-10-30 16:12:05 UTC
Wikibase uses "q123" for item IDs but "Q123" for the corresponding page title. The API should accept both form of the ID, for conveniance. The ID is still unique, we just define the prefix to be case-agnostic.
Comment 1 jeblad 2012-10-30 17:15:41 UTC
Force lower case on ids in the API? Or make a method to normalize just the prefix into a known form?
Comment 2 Daniel Kinzler 2012-10-30 17:54:54 UTC
I think EntityContentFactory::getFromPrefixedId should simply accept upper- and lower case prefixes. Is there anything else that would need changing?
Comment 3 Daniel Kinzler 2012-10-30 17:55:18 UTC
Or rather, EntityContentFactory::getEntityTypeFromPrefixedId
Comment 4 denny vrandecic 2012-11-08 11:22:47 UTC
Confirmed. On the dev system it still has this behavior.
Comment 5 Kunal Mehta (Legoktm) 2013-08-31 09:41:53 UTC
https://www.wikidata.org/w/api.php?action=wbgetentities&ids=Q441536&format=jsonfm this was fixed at some point.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links