@artsy/cohesion - npm Package Compare versions

Comparing version 0.2.8-canary.29.494.0 to 0.2.8-canary.29.499.0

package.json

		{
		"name": "@artsy/cohesion",
		"version": "0.2.8-canary.29.494.0",
		"version": "0.2.8-canary.29.499.0",
		"description": "Analytics schema and library helpers",
		@@ -5,0 +5,0 @@ "main": "dist/index.js",

README.md

		@@ -57,5 +57,5 @@ # Cohesion [![CircleCI](https://circleci.com/gh/artsy/cohesion.svg?style=svg)](https://circleci.com/gh/artsy/cohesion) [![npm version](https://badge.fury.io/js/%40artsy%2Fcohesion.svg)](https://www.npmjs.com/package/@artsy/2Fcohesion)

		2. In `Event.ts`, create an interface describing the shape of the new event, as it is recieved in Segment/Redshift.
		2. In `Schema/Event.ts`, create an interface describing the shape of the new event, as it is recieved in Segment/Redshift.

		The `action` key is required and should match the `ActionType` created in step 1.
		- The `action` key is required and should match the `ActionType` created in step 1.

		@@ -73,3 +73,3 @@ ```typescript

		3. If your event uses values not yet in the schema, such as a new `ContextModule`, add new values to existing enums in the Schema directory.
		3. If your event uses values not yet in the schema, such as a new `ContextModule`, add new values to the existing typings in the Schema directory.

		@@ -86,2 +86,2 @@ 4. Add descriptive comments with examples to explain the use of your new event. Our documentation is generated automatically from in-code comments, find more information on syntax in the [`typedoc` docs](https://typedoc.org/guides/doccomments/).

		Engineers should use these helpers whenever sending analtics data to Segment, for example, when creating and analytics event with `react-tracking`.
		Engineers should use these helpers whenever sending analtics data to Segment, for example, when creating an analytics event with `react-tracking`.

@artsy/cohesion - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics