| dbarratt added a comment. |
In T173214#4442721, @Tpt wrote:It could definitely be used now but without any stability guaranties. The GraphQL query resolution is a bit heavy because it makes a lot of requests to the API but for light usages it should be definitely possible to use it. I am still not happy with everything, especially the data values access that is indeed not very user friendly.
Yeah there might be some opportunities to simplify/flatten the access a bit. I'm not sure how this could be done other than making the properties themselves types? Though there might be way too many properties to do that, and as you mentioned, it would have to be rebuilt every time a property changes. Although, I kinda doubt that the type of a property changes very often (if at all?), so they could be cached for a long time and it could be done within an extension or within wikibase itself dynamically. I don't think it's a big deal that it would be different for every wikibase instance, the API (Special:EntityData & SPARQL) is already different for each instance of wikibase, so as long as the introspection works correctly, I think it's fine (or even preferred) if it doesn't try to be the same across instances.
Cc: Addshore, larsgw, Saerdnaer, simon04, bearND, Siznax, Tpt, Jonas, Ricordisamoa, hoo, Lucas_Werkmeister_WMDE, Aklapper, dbarratt, PokestarFan, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
