[Wikidata-bugs] [Maniphest] [Commented On] T232193: Research statement saving

2019-09-10 Thread Tarrow
Tarrow added a comment. In T232193#5474967 , @Lucas_Werkmeister_WMDE wrote: > If you need more data in the hook, you can just add extra arguments to it without making an incompatible change (or am I misunderstanding something?).

[Wikidata-bugs] [Maniphest] [Commented On] T232193: Research statement saving

2019-09-09 Thread Lucas_Werkmeister_WMDE
Lucas_Werkmeister_WMDE added a comment. In T232193#5474884 , @Tarrow wrote: > We are imagining perhaps altering StatementChanger.js with something like If you need more data in the hook, you can just add extra arguments to it

[Wikidata-bugs] [Maniphest] [Commented On] T232193: Research statement saving

2019-09-09 Thread Tarrow
Tarrow added a comment. We are imagining perhaps altering StatementChanger.js with something like // Step 1 introduce: self._fireHook( 'wikibase.statement.savedWithContext', self._entity, statement );

[Wikidata-bugs] [Maniphest] [Commented On] T232193: Research statement saving

2019-09-09 Thread noarave
noarave added a comment. Assuming we are interested in knowing when a statement's value have been changed, here's what I was able to find so far: - StatementChanger.js method save() has the object statement where the element claim (originates in Claim.js) lies. -