You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Decide how far the source proxy generator grows toward the .NET generator #50
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.
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.
Activity
woksin commentedon Oct 1, 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.woksin commentedon Oct 2, 2026
Decided in https://github.com/Cratis/Arc.TypeScript/blob/main/decisions/0001-keep-proxy-generation-focused-on-client-contracts.md (#170). Follow-ups: #166, #167.