• State: In development
• GitHub: https://github.com/artsy/cohesion
• Docs: https://cohesion.artsy.net
• Ci: https://circleci.com/gh/artsy/cohesion
• NPM: Package updates are published automatically on successful merges to main. Canaries are available on PR's from feature branches.
• Point People: @abhitip

Requirements: Yarn

yarn install

yarn test

yarn docs

To view docs locally, visit the full filepath of docs/index.html in your browser, i.e, file:///Users/<MY_USER>/<MY_LOCAL_DIRECTORY>/cohesion/doc/index.html

The /Schema directory represents the Artsy's analytics schema, and describes expectations for data consumed by Redshift and Segment.

This schema is maintained by Artsy's data team, engineers should not expect to change these files.

Valid analytics events are described in /Schema/Events/index.ts, and individual event schemas live in the Schema/Events directory, divided by concern.

Typings for all allowed values, such as ContextModule, are exported for use by engineers in consuming projects.

1. In Schema/Events, add the name of the new event. This name defines the corresponding downstream table's name in Redshift, and should use the lowerCamelCase naming convention.

// Schema/Events/index.ts

export enum ActionType {
  ...
  myNewEvent = "myNewEvent",
  ...
}

2. In Schema/Events directory, create a new interface describing the shape of the new event, as it is received in Segment/Redshift.

• The name of the interface should match the ActionType created in step 1, but use the UpperCamelCase naming convention.
• The action key is required and should match the ActionType created in step 1.
• 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.

// Schema/Events/MyNewEvent.ts

export interface MyNewEvent {
  action: ActionType.myNewEvent
  context_module: ContextModule
  optional_property?: string
  required_property: number
}

3. In Schema/Events/index.ts, add the new interface to the valid events main list, Event

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.

5. If you have created any new files, add an export statement to Schema/index.ts like so:

// Schema/index.ts

export * from "./Events/MyNewEvent"

6. PR your changes. Once merged, the schema will be updated and your new event and values will be available to consumers of this package.