Coming from…
Concept maps from NestJS, ASP.NET Core and Laravel to effx annotations and the Effect constructs underneath.
effx keeps a declarative surface that teams on enterprise frameworks already know, and generates ordinary Effect underneath (ADR 0012). These pages map each framework's concepts to effx and say, row by row, what is supported, what comes via an ecosystem package, and what is a gap.
| Status | Meaning |
|---|---|
| supported | implemented in effx; the row cites a spec or source path |
| via ecosystem package | an Effect package does it; effx does not reimplement it |
| gap | nothing today; not called "planned" unless a spec says so |
NestJS
Controllers, pipes, guards and filters to operations, contracts and access.
ASP.NET Core
Controllers, policies and ProblemDetails to operations, access and problems.
Laravel
Form requests, policies and exception rendering to operations, access and problems.
Each framework claim cites that framework's official documentation. Each effx claim cites a spec or a source path.
Getting started
Walk the examples/users slice end to end, from declarations to check, build, inspect, graph, and a running server, client and CLI.
Coming from NestJS
A concept map from NestJS controllers, pipes, guards and filters to effx annotations and the Effect constructs underneath, a list of gaps, and one endpoint ported side by side.