Change Details

(TODO: this is linked to from https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/EventLogging/+/463501/, as part of the deprecation message. It needs to be filled out with instructions on how to update eventlogging instrumentation after that change is merged.)

=Quick Summary= ---------------------- * You can now directly use `mw.loader.using( 'ext.eventLogging' ).then( ... use mw.eventLog.logEvent to log events as before ... )` * This will no longer validate your events * To validate events, enable debug mode by setting `eventlogging-display-web` to 1 =The Detail= ---------------- With T187207 we changed the EventLogging javascript client. We removed validation of events and stripped out ResourceLoader schema modules. So, before this change you would do: mw.loader.using( 'schema.NavigationTiming' ).then( () => mw.eventLog.logEvent( 'NavigationTiming', { isAnon: true } ) ); (no, they won't let you use inline functions :(, but it's just docs so I can be fancy). This worked as follows: * the NavigationTiming schema ResourceLoader module contained the schema json, which was added to `mw.eventLog.schemas` with `declareSchema`. * this module also depends on `ext.eventLogging`, so `using` it also prepares `mw.eventLog`. * the call to `mw.eventLog.logEvent` validated the event you passed against the schema and sent it regardless of validation result Now, **after this change**, you have two options:

(TODO: this is linked to from https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/EventLogging/+/463501/=Quick Summary= ---------------------- * You can now directly use `mw.loader.using( 'ext.eventLogging' ).then( ... use mw.eventLog.logEvent to log events as before ... )` * This will no longer validate your events * To validate events, enable debug mode by setting `eventlogging-display-web` to 1 =The Detail= ---------------- With T187207 we changed the EventLogging javascript client. We removed validation of events and stripped out ResourceLoader schema modules. So, before this change you would do: mw.loader.using( 'schema.NavigationTiming' ).then( () => mw.eventLog.logEvent( 'NavigationTiming', { isAnon: true } ) ); (no, they won't let you use inline functions :(, as part of the deprecation messagebut it's just docs so I can be fancy). It needs to be filled out with instructions on how to update eventlogging instrumentation after that change is merged.)This worked as follows: * the NavigationTiming schema ResourceLoader module contained the schema json, which was added to `mw.eventLog.schemas` with `declareSchema`. * this module also depends on `ext.eventLogging`, so `using` it also prepares `mw.eventLog`. * the call to `mw.eventLog.logEvent` validated the event you passed against the schema and sent it regardless of validation result Now, **after this change**, you have two options: