The state-machine builder with the call chains needs very proper exception handling, otherwise the Sender object can stay in an unusable state, e.g. .table() will always raise because it has already been set.
Would be cool to have a simple .write() function that captures everything at once. The underlying protocol is quite simple and there is no need to have the state builder, or is there?
JS is a concurrent async language and local states on shared mutable objects can be a pain, especially when there is an async call in the loop such as sender.at().
The state-machine builder with the call chains needs very proper exception handling, otherwise the Sender object can stay in an unusable state, e.g.
.table()will always raise because it has already been set.Would be cool to have a simple
.write()function that captures everything at once. The underlying protocol is quite simple and there is no need to have the state builder, or is there?JS is a concurrent async language and local states on shared mutable objects can be a pain, especially when there is an async call in the loop such as
sender.at().