Release/5.2.0

[matus-tomlein]

Tracker plugins provide a new filter callback that enables you to add custom logic that decides whether a given event should be tracked or not. This can for example enable you to intercept events automatically tracked by the tracker and skip some of them. For instance, the following code will apply to all screen view events and only accept ones with the name "Home Screen", other screen view events will be discarded:

plugin.filter(schemas: [
    "iglu:com.snowplowanalytics.snowplow/screen_view/jsonschema/1-0-0", // screen view events
]) { event in
    return event.payload["name"] as? String == "Home Screen"
}

Finally, you can now provide a configuration version for default configuration used in the remote configuration setup. This makes sure that the tracker is only reloaded when a newer configuration is available on the remote endpoint than the default one.

Enhancements

• Add a filter API to plugins to decide whether to track an event or not (Add a filter API to plugins to decide whether to track an event or not #783)
• Add version to default remote configuration and don't update unless remote configuration is newer (Add version to default remote configuration and don't update unless remote configuration is newer #779)

Under the hood

• Handle unprotected access to sending state in Emitter from concurrent threads (Data race in Emitter and unfortunate handling of threads #774)

[mscwilson]

LGTM!
except - the codeblock in the PR description is in Kotlin