Custom exporters

Learn about building custom exporters.

null

All exporter packages are backed by GitHub repositories, so they can take advantage of all GitHub features like forking, distributing versions, or even provide a familiar place to report issues or feature requests directly to the author.

null

Cloning and customizing existing exporters

null

If you would like to make your own edits to an existing public exporter in the exporter store, this can be done with cloning.

  1. In Code automation → Exporters, locate the exporter you would like to clone.
  2. Click the GitHub button to view it on GitHub.
  3. In GitHub, fork the repository.
  4. Optional — if you would like to make this exporter public, you must change the unique package identifier.
  5. In Code automation → Exporters → Custom, click + New custom exporter, and provide the URL of the forked repository.
  6. Click Create exporter.

The cloned exporter will now be available in your workspace.

null

This is a summary. For detailed information on building custom exporters, please refer to the section Customizing existing exporters in the developer documentation.


Building custom exporters

We recognize that everyone's requirements and coding standards are different, and that the file structure of the export can be vastly different from project to project — which is why we allow you to build your own private custom exporters.

Detailed information about why, how and when to build your own custom exporters can be found in our Developer documentation.