[Wikidata-bugs] [Maniphest] T277826: Add a new qualifier for the conflicts-with constraint to specify the properties and values that should be used instead

2023-01-03 Thread Agabi10
Agabi10 removed Agabi10 as the assignee of this task. Agabi10 added a comment. Due to lack of time I didn't work in this in months and even if I might get into this later again I prefer unasigning myself from the task for now to avoid discouraging others from working on the task. TASK DETAIL

[Wikidata-bugs] [Maniphest] T277826: Add a new qualifier for the conflicts-with constraint to specify the properties and values that should be used instead

2022-05-16 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. Include two line breaks in the source (`\n\n` – you can often see that in `qqq.json` before the list of parameters for a message, for example), then it’ll be wikitext-parsed as a paragraph break. TASK DETAIL https://phabricator.wikimedia.org/T277826

[Wikidata-bugs] [Maniphest] T277826: Add a new qualifier for the conflicts-with constraint to specify the properties and values that should be used instead

2022-05-13 Thread Agabi10
Agabi10 added a comment. In T277826#7926652 , @Lucas_Werkmeister_WMDE wrote: > For the multi-multi case I would suggest a message with more than one paragraph, something like: > >> An entity should not have statements for both $1 and

[Wikidata-bugs] [Maniphest] T277826: Add a new qualifier for the conflicts-with constraint to specify the properties and values that should be used instead

2022-05-13 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. I would prefer to avoid interpreting the constraint too much, and limit the message to something like “Use the value video game developer instead.” The user can hopefully make a better decision about what a correct fix looks like. (But yes, making the

[Wikidata-bugs] [Maniphest] T277826: Add a new qualifier for the conflicts-with constraint to specify the properties and values that should be used instead

2022-05-13 Thread Agabi10
Agabi10 added a comment. In T277826#7926652 , @Lucas_Werkmeister_WMDE wrote: > Note that it’s also possible to have only a replacement value but no replacement property. In this case should I assume that the same property with a dif

[Wikidata-bugs] [Maniphest] T277826: Add a new qualifier for the conflicts-with constraint to specify the properties and values that should be used instead

2022-05-13 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. Note that it’s also possible to have only a replacement value but no replacement property. Query of conflicts-with constraints with replacements.

[Wikidata-bugs] [Maniphest] T277826: Add a new qualifier for the conflicts-with constraint to specify the properties and values that should be used instead

2022-05-12 Thread Agabi10
Agabi10 claimed this task. Agabi10 added a comment. I started working on this, but I'm not sure how should I handle the messages when multiple properties and multiple values are specified with the replacement property and replacement value qualifiers. When only one property is provided I

[Wikidata-bugs] [Maniphest] T277826: Add a new qualifier for the conflicts-with constraint to specify the properties and values that should be used instead

2021-07-11 Thread Esc3300
Esc3300 renamed this task from "Add a new qualifier for the conflicts-with constraint to specify the properties that should be used instead" to "Add a new qualifier for the conflicts-with constraint to specify the properties and values that should be used instead". Esc3300 updated the task descr