EndpointServerLogicOps
Value members
Concrete methods
Combine this public endpoint description with a function, which implements the server-side logic. The logic returns a result, which is
either an error or a successful output, wrapped in an effect type F
. For secure endpoints, use serverSecurityLogic.
Combine this public endpoint description with a function, which implements the server-side logic. The logic returns a result, which is
either an error or a successful output, wrapped in an effect type F
. For secure endpoints, use serverSecurityLogic.
A server endpoint can be passed to a server interpreter. Each server interpreter supports effects of a specific type(s).
Both the endpoint and logic function are considered complete, and cannot be later extended through the returned ServerEndpoint value (except for endpoint meta-data). Secure endpoints allow providing the security logic before all the inputs and outputs are specified.
Like serverLogic, but specialised to the case when the result is always an error (Left
), hence when the logic type can be
simplified to I => F[E]
.
Like serverLogic, but specialised to the case when the result is always an error (Left
), hence when the logic type can be
simplified to I => F[E]
.
Like serverLogic, but specialised to the case when the logic function is pure, that is doesn't have any side effects.
Like serverLogic, but specialised to the case when the logic function is pure, that is doesn't have any side effects.
Same as serverLogic, but requires E
to be a throwable, and coverts failed effects of type E
to endpoint errors.
Same as serverLogic, but requires E
to be a throwable, and coverts failed effects of type E
to endpoint errors.
Like serverLogic, but specialised to the case when the result is always a success (Right
), hence when the logic type can be
simplified to I => F[O]
.
Like serverLogic, but specialised to the case when the result is always a success (Right
), hence when the logic type can be
simplified to I => F[O]
.
Combine this endpoint description with a function, which implements the security logic of the endpoint.
Combine this endpoint description with a function, which implements the security logic of the endpoint.
Subsequently, the endpoint inputs and outputs can be extended (for error outputs, new variants can be added, but they cannot be arbitrarily extended). Then the main server logic can be provided, given a function which accepts as arguments the result of the security logic and the remaining input. The final result is then a ServerEndpoint.
A complete server endpoint can be passed to a server interpreter. Each server interpreter supports effects of a specific type(s).
An example use-case is defining an endpoint with fully-defined errors, and with security logic built-in. Such an endpoint can be then extended by multiple other endpoints, by specifying different inputs, outputs and the main logic.
Like serverSecurityLogic, but specialised to the case when the result is always an error (Left
), hence when the logic type can
be simplified to A => F[E]
.
Like serverSecurityLogic, but specialised to the case when the result is always an error (Left
), hence when the logic type can
be simplified to A => F[E]
.
Like serverSecurityLogic, but specialised to the case when the logic function is pure, that is doesn't have any side effects.
Like serverSecurityLogic, but specialised to the case when the logic function is pure, that is doesn't have any side effects.
Same as serverSecurityLogic, but requires E
to be a throwable, and coverts failed effects of type E
to endpoint errors.
Same as serverSecurityLogic, but requires E
to be a throwable, and coverts failed effects of type E
to endpoint errors.
Like serverSecurityLogic, but specialised to the case when the result is always a success (Right
), hence when the logic type can
be simplified to A => F[U]
.
Like serverSecurityLogic, but specialised to the case when the result is always a success (Right
), hence when the logic type can
be simplified to A => F[U]
.