@adobe/reactor-turbine-schemas

A collection of schema used for validation of JSON objects within Launch.

Stats

StarsIssuesVersionUpdatedCreatedSize
@adobe/reactor-turbine-schemas
10.3.02 months ago5 years agoMinified + gzip package size for @adobe/reactor-turbine-schemas in KB

Readme

@adobe/reactor-turbine-schemas

Experience Platform Tags, by Adobe, is a next-generation tag management solution enabling simplified deployment of marketing technologies. For more information regarding Experience Platform Tags, please visit our product website.

This project is a collection of schemas based on the JSON Schema vocabulary that are used for validation of JSON objects within Experience Platform Tags. The schemas are not intended to be used directly by consumers; they are used by the Experience Platform Tags system and extension development tools.

Available Schemas

container.json

A schema describing the "container" output for Turbine (Web) (the Experience Platform Tags rule engine). The container object contains configuration specific to an Experience Platform Tags property. Turbine uses the container as instruction on how to behave when running on a client website.

extension-package-web.json

A schema describing the extension.json found in a web extension package. The extension.json file describes the contents of an extension. More information can be found on the extension development guide.

extension-package-mobile.json

A schema describing the extension.json found in a web extension package. The extension.json file describes the contents of an extension.

Contributing

Contributions are welcomed! Read the Contributing Guide for more information.

To get started:

  1. Install node.js.
  2. Clone the repository.
  3. After navigating into the project directory, install project dependencies by running npm install.

Scripts

To run tests a single time, run the following command:

npm run test

Licensing

This project is licensed under the Apache V2 License. See LICENSE for more information.

If you find any bugs or have a feature request, please open an issue on github!

The npm package download data comes from npm's download counts api and package details come from npms.io.