Releases · timing71/chrome

Further fixes to replay generation
Add the ability to mark past sessions as "safe from deletion" - such marked sessions will not be deleted automatically

Assets 2

01 Jun 11:55

v1.5.0

Fix a bug with replay generation that would cause skipped frames and inconsistent data.
Update to @timing71/common package v0.6.0.

Assets 3

13 Jun 15:52

v1.4.0

Assets 2

19 Apr 12:58

v1.3.0

Add support for specifying WebSocket subprotocols (necessary to support GraphQL subscriptions).

Assets 2

03 Nov 11:40

v1.2.0

Assets 2

05 Jun 10:46

v1.1.0

Allow services to store arbitrary transient data.
- This is intended to allow services to persist certain internal state so that it can be recovered if the service is restarted (e.g. the browser page is refreshed).
Support multiple sessions from one service instance.
- This, combined with the related changes to @timing71/common, allows services to declare session changes, and keep separate sessions' data separate. Take, for example, a service that's running all day; previously you'd have one set of data with each track session that day (practices, qualifying, support races...) and no easy way to separate them out. Now, if services can detect a session change, they can store each session separately.
Move IndexedDB access to extension-space code. This resolves an issue where some services would not work without third-party cookies enabled in Chrome.
Recent sources list is now stored separately to recent sessions; this preserves the list even when recent sessions are expired.
Fixed a bug in file naming if the service name or description contained a slash.
Added button linking to the T71 Archive to the browser extension menu.