| Lucas_Werkmeister_WMDE added a comment. |
My current idea is to do this after T171743: Introduce constraint check context abstraction with a new kind of context, which contains only an entity ID and no snak. We’ll have some kind of “scheduler”(?) that takes a plan of contexts and constraints to run, and downgrades the context for some constraint types to an entity-only context and then deduplicates the plan.
Also, I think the full list of constraint type that this applies to is just:
- conflicts with
- item requires statement
- type
TASK DETAIL
EMAIL PREFERENCES
To: Lucas_Werkmeister_WMDE
Cc: thiemowmde, Jonas, Lucas_Werkmeister_WMDE, Aklapper, GoranSMilovanovic, QZanden, Agabi10, Izno, Wikidata-bugs, aude, Mbch331
Cc: thiemowmde, Jonas, Lucas_Werkmeister_WMDE, Aklapper, GoranSMilovanovic, QZanden, Agabi10, Izno, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
