The term "Zapps" refers to collections of Specifications, Schemas, Generators, Templates, Engines, and Processors organized for a specific project or module. A Zapp serves as a self-contained ecosystem for automating your code generation tasks. This section will help you understand what Zapps are, how to create them, and how they can be beneficial in streamlining your development workflow.

What Are Zapps?

Zapps are essentially configurations or blueprints that organize all the necessary elements for code generation in Zapp. By grouping these elements, a Zapp provides an efficient way to manage complex projects and ensures that all generated code follows the same guidelines and standards.

Creating a Zapp

To create a Zapp, you need to define a configuration file that describes all the components involved in the code generation lifecycle for a given project. This file is often named zapp.config.yaml or zapp.config.json, depending on your preferred format.

Here's a basic example of a Zapp in TypeScript:

export const ServiceZapp: IServiceZapp = (spec) => {
  const files: ZappFile = {
    ['src/db.ts']: DbGenerator({
      models: spec.models,
    ['LICENSE']: LicenseGenerator({
    ['']: ReadmeGenerator({

  Object.entries(spec.calls).forEach(([name, call]) => {
    files[`src/calls/${name}.ts`] = CallGenerator(call);

  Object.entries(spec.models).forEach(([name, model]) => {
    files[`src/models/${name}.ts`] = ModelGenerator(model);

  return files;

Benefits of Using Zapps

Here are some of the key advantages:

  • Organization: Keeps all components related to code generation neatly arranged.
  • Reusability: Allows for the reuse of Schemas, Generators, Templates, and other components across different parts of a project or even different projects.
  • Consistency: Helps maintain a uniform code style and structure across the codebase.
  • Efficiency: Streamlines the process of updating and maintaining your code.

Using Zapps in a Team Setting

Zapps are particularly useful in a team setting where multiple developers are working on the same codebase. The Zapp configuration ensures that everyone is using the same Specifications, Schemas, and Generators, thereby maintaining code consistency.

Version Control

It's a good practice to version-control your Zapps, just like you would with your codebase. This allows for effective tracking of changes, easy rollback to previous versions, and sharing configurations among team members.

Best Practices

  • Documentation: Always document your Zapp configurations to ensure that team members can easily understand the setup.
  • Modular Design: Create Zapps for specific modules or services within a larger project to make it easier to manage.
  • Regular Updates: Keep your Zapps up-to-date with any changes in Specifications, Templates, or other components to ensure optimal performance.

By understanding and effectively using Zapps, you can significantly enhance your development workflow, keeping your projects organized, consistent, and efficient.