Change Details

##**(!) Ticket depends on the outcome of T415380** The indicators and messages provided by WikibaseQualityConstraints draw a user's attention to issues that should be fixed. When they make an edit that fixes these issues, it's reasonable to expect that the error should go away. On desktop, this happens as expected. Currently in MEX, the errors persist regardless of whether they are fixed. Additionally, if a violation is introduced by an edit, the user gets no indication of this until the page is refreshed. Depending on how we implement violation-clearing, we might get violation-introduction "for free". Or it might make sense for this to be a separate ticket. === Acceptance Criteria - [ ] after saving an edit that corrects a violation, that violation is removed - [ ] after saving an edit that introduces a violation, an indicator and message about it is added (TODO: decide whether this belongs in its own ticket) - [ ] the addition or removal of a violation does not affect the existence of *other* violations

The indicators and messages provided by WikibaseQualityConstraints draw a user's attention to issues that should be fixed. When they make an edit that fixes these issues, it's reasonable to expect that the error should go away. On desktop, this happens as expected. Currently in MEX, the errors persist regardless of whether they are fixed. Additionally, if a violation is introduced by an edit, the user gets no indication of this until the page is refreshed. === Acceptance Criteria - [ ] after saving an edit that corrects a violation, that violation is removed. - [ ] after saving an edit that introduces a violation, an indicator and message about it is added. - [ ] Test coverage should be implemented.

##**(!) Ticket depends on the outcome of T415380** The indicators and messages provided by WikibaseQualityConstraints draw a user's attention to issues that should be fixed. When they make an edit that fixes these issues, it's reasonable to expect that the error should go away. On desktop, this happens as expected. Currently in MEX, the errors persist regardless of whether they are fixed. Additionally, if a violation is introduced by an edit, the user gets no indication of this until the page is refreshed. Depending on how we implement violation-clearing, we might get violation-introduction "for free". Or it might make sense for this to be a separate ticket. === Acceptance Criteria - [ ] after saving an edit that corrects a violation, that violation is removed. - [ ] after saving an edit that introduces a violation, an indicator and message about it is added (TODO: decide whether this belongs in its own ticket). - [ ] the addition or removal of a violation does not affect the existence of *other* violations Test coverage should be implemented.