Skip to content

dotnet new Connector Scaffold #64

Description

@tsutomi

"The fastest path to a correct connector is starting from one that already compiles."

The Problem Today

There is no formal starting point for implementing a new connector. Contributors must infer the expected project structure, base class overrides, capability declarations, DI registration pattern, and xUnit test helper conventions by reading existing connectors — a slow and error-prone process.

What We Are Building

A dotnet new template package (Ratatosk.Connector.Templates) that generates a fully wired connector solution: the connector project with correct base class overrides and a IChannelSchema factory, a companion xUnit test helper package, and a minimal usage sample — all pre-configured and immediately buildable.

Benefits

  • New connectors compile and pass a baseline test suite from the first dotnet build
  • Naming conventions, project layout, and package references are consistent across all connectors
  • Lowers the barrier for community contributions

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request
    No fields configured for Feature.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions