Skip to content

Decide how far the source proxy generator grows toward the .NET generator #50

Description

@woksin

The TypeScript proxy generator reads TypeScript source and writes proxies for the published @cratis/arc client. It covers the commands, queries, observable queries, concepts, enums and validation rules the Tasks and Library samples need, but not everything Arc's .NET proxy generator supports: for example namespace-root remapping, package/type import mappings, exclusions and library-model export.

Decide which of the .NET generator's options and outputs the TypeScript generator should support, and in which order. A byte-level comparison against pinned .NET proxy output would make the remaining differences visible.

Activity

  1. self-assigned this
    on Sep 27, 2026
  2. woksin commented on Oct 1, 2026

    @woksin
    ContributorAuthor

    Status: package and type import mappings in generated proxies shipped in v0.52.0 (#141, closing #113), and opt-out React hooks (--skip-react-hooks) in v0.51.0. Namespace-root remapping, exclusions and library-model export are still not supported, and the byte-level comparison against pinned .NET output has not been done. The decision on order and scope is still open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

questionFurther information is requested

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions