Decide how far the source proxy generator grows toward the .NET generator #50
Copy link
Copy link
Closed
Labels
questionFurther information is requestedFurther information is requested
Description
Activity
- addedquestionFurther information is requestedFurther information is requested
on Sep 25, 2026 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.
Metadata
Metadata
Assignees
Labels
questionFurther information is requestedFurther information is requested
The TypeScript proxy generator reads TypeScript source and writes proxies for the published
@cratis/arcclient. 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.