engine icon indicating copy to clipboard operation
engine copied to clipboard

Calling a service defined in browser environment from node environment should be an error

Open alisey opened this issue 3 years ago • 0 comments

Currently, when calling a service defined in a single-endpoint browser environment from a node environment, the engine either completes the request, or leaves it in a pending state indefinitely (if there are no browser environments running at the time of the request).

Instead, the engine should throw an error to prevent incorrect usage. Maybe we could even guarantee this at compile time instead of throwing a runtime error?

alisey avatar Mar 22 '21 14:03 alisey