"Perhaps I'm missing something, but at least for the QuantityHandler, I could not see where the actual search behavior is tested. E.g. if I search for 12+/-2, the value 11+/-1 should be fouund, but the value 10+/-5 should not. This needs to be tested somewhere."
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T52911 Support transitive queries | |||
| Resolved | None | T54387 Special page for querying by one property and value | |||
| Declined | Lydia_Pintscher | T54385 Query by one property and one value ("simple queries") (tracking) | |||
| Invalid | Lydia_Pintscher | T69080 [Story] Implement range queries for uncertain values (geo, time, quantities) | |||
| Invalid | Lydia_Pintscher | T78659 [Task] Test actual search logic |
Event Timeline
Comment Actions
This is waiting for review/merge for 3 months now: https://github.com/wmde/WikibaseQueryEngine/pull/114
Comment Actions
@Lydia_Pintscher @thiemowmde why the raised priority and new activity here? I was under the impression we where not continuing with our own queries. Do we have a new plan?
Comment Actions
We might come back to this for what we currently call "stupid queries". But we obviously can not use a component with zero integration tests. The integration tests are there but not reviewed and not merged for 13 months now:
Comment Actions
We decided to not work on this given that the SPARQL endpoint seems to be working well and covering most usecases.