Santiago Tortosa
Santiago Tortosa
[The documentation for `:cowboy_websocket`](https://ninenines.eu/docs/en/cowboy/2.4/manual/cowboy_websocket/) states that the `websocket_init/1` callback can return values specified in the `CallResult` type. However, the current implementation of `Endpoint.Cowboy2Handler` **forces** the return from the handler/transport `Socket.Transport.init/1`...
Starting a rewrite as of today, mainly aiming for an async lightweight system with integrated voice. Any help or suggestion, mostly about possible structure tweaks, is welcome. If you feel...
The `c:Commanded.Event.Handler.handle/2` callback allows returning an `{:ok, state}` tuple. But the typespec of our `c:after_update/3` callback does not include this.
The current behaviour of `Ecto.Enum.cast/2` is that only an `:error` atom is returned in case of error: ```elixir params = Ecto.Enum.init(values: [foo: 1, bar: 2, baz: 5]) assert :error =...
From [the `Postgrex.Notifications` documentation](https://hexdocs.pm/postgrex/Postgrex.Notifications.html#module-async-connect-auto-reconnects-and-missed-notifications): > Note however that when the notification system is waiting for a connection, any notifications that occur during the disconnection period are not queued and cannot...
The `listen_to` parameter is the registered name of the `Postgrex.Notifications` process that is used to listen for event notifications. That process is not monitored from `Notifications.Listener`. If the `Postgrex.Notifications` process...
This would allow specifying a custom dispatch timeout for each ProcessManager rather than having to fiddle with the global timeout.