Change Details

=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: * keep `using( 'schema.<<your schema>>' )` but these modules will be completely removed at some point. For now, for backwards compatibility we just emptied them out and kept their dependency on `ext.eventLogging`. * switch to using the subscriber module (preferred) or use `ext.eventLogging`.

=Quick Summary= ---------------------- f you are using `mw.track( 'event.SchemaName', .. )`, there is nothing to migrate. If you are using `mw.eventLog.logEvent`, then there is no longer any need to load `schema.*` modules. You can now directly use `mw.loader.using( 'ext.eventLogging' ).then(... use mw.eventLog.logEvent as before ...)`. EventLogging will no longer validate your events client-side on every page view by default. To automatically validate events, enable debug mode by setting the `eventlogging-display-web` user preference, see [Debug mode](https://doc.wikimedia.org/EventLogging/master/js/#!/api/mw.eventLog.Debug) to learn how. =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: ```lang=js mw.loader.using( 'schema.Example' ).then( () => { mw.eventLog.logEvent( 'Example', { some: 'data', here: true } ) ); } ); ``` //(no, they won't let you use arrow functions :(, but it's just docs so I can be fancy).// This worked as follows: * the `schema.Example` module contained the schema json, which was added to `mw.eventLog.schemas` //(private)// with `declareSchema` //(private)//. * this module also depended on `ext.eventLogging`, so `using` it also provided `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 migration options: For backwards compatibility, the schema modules still exist. We just emptied them out and kept their dependency on `ext.eventLogging` with a deprecation warning. * Switch to `using( 'ext.eventLogging' )` before the schema modules are completely removed in the future. * Switch to the lightweight subscriber method (preferred), via `mw.track()`.

=Quick Summary= ---------------------- f you are using `mw.track( 'event.SchemaName', .. )`, there is nothing to migrate. If you are using `mw.eventLog.logEvent`, then there is no longer any need to load `schema.*` modules. * You can now directly use `mw.loader.using( 'ext.eventLogging' ).then( ... use mw.eventLog.logEvent to log events as before ...as before ...)`. EventLogging will no longer validate your events client-side on every page view by default. To automatically validate events, )` * This will no longer validate your events * To validate events, enable debug mode by setting `eventlogging-display-web` to 1enable debug mode by setting the `eventlogging-display-web` user preference, see [Debug mode](https://doc.wikimedia.org/EventLogging/master/js/#!/api/mw.eventLog.Debug) to learn how. =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: ```lang=js mw.loader.using( 'schema.NavigationTimingExample' ).then( () => mw{ mw.eventLog.logEvent( 'NavigationTiming'Example', { some: 'data', { isAnonhere: true } ) );; } ); ``` //(no, they won't let you use inlinearrow functions :(, but it's just docs so I can be fancy).// This worked as follows: * the NavigationTiming `schema ResourceLoader.Example` module contained the schema json, which was added to `mw.eventLog.schemas` //(private)// with `declareSchema` //(private)//. * this module also dependsed on `ext.eventLogging`, so `using` it also preparesprovided `mw.eventLog`. * the call to `mw.eventLog.logEvent` validated the event you passed against the schema and sent itit, regardless of validation result. Now, **after this change**, you have two migration options: * keep `using( 'schema.<<your schema>>' )` but these modules will be completely removed at some point. For now, for backwards compatibility we just emptied them out and kept their dependency on `ext.eventLogging`. * switch to using the subscriber module (preferred) or use `ext.eventLoggingFor backwards compatibility, the schema modules still exist. We just emptied them out and kept their dependency on `ext.eventLogging` with a deprecation warning. * Switch to `using( 'ext.eventLogging' )` before the schema modules are completely removed in the future. * Switch to the lightweight subscriber method (preferred), via `mw.track()`.