# CLI Enhancement: Multi-Protocol Support 🚀

[qballer]

Background

Contractual needs to support any API boundary (client-to-server, server-to-server) regardless of the protocol being used. While we currently support OpenAPI, we need to expand to other protocols like Protobuf and JSON Schema to serve diverse API architectures better.

Proposed CLI Structure 📋

Directory Structure

contractual/
├── tsps/                      # TypeSpec source files
└── protocols/            # Generated protocol files
    ├── specs/               # OpenAPI output
    ├── protos/              # Protobuf output
    └── schemas/         # JSON Schema output

Core Commands to Implement

1. contractual init ✨

   • Creates the directory structure above

2. contractual (root command)

   • Lists all .tsp files in the tsps directory
   • Shows their current protocol outputs

3. contractual contract [.tsp name] 🔧

   • Generates client/server code from TSP
   • Flags: --server-only, --client-only

4. contractual version [.tsp name]

   • Handles versioning across protocols
   • Prompts for version bumps

5. contractual diff [.tsp name] 🔍

   • Shows differences between current TSP and protocol outputs

Questions to Resolve

• Should we support protocol-specific configurations?
• @omermorad, we discussed a toml file that configures type spec. This seems relevant.
• This implies that the protocol is deduced from the type spec file. How can we achieve this?