todo
chase-moskal opened this issue · 0 comments
chase-moskal commented
- 🔥 smarter error handling
- probably have
ExposedError
orPublicError
, which the user can extend to indicate that such errors can be safely exposed/published - maybe rename
exposeErrors
option to something likeexposeAllUnknownErrors
- probably have
- refactor to extract json-rpc batch handling for http/websocket into
s/comms/
- currently each transport does its own funky adhoc implementation
- test suites
- postMessage
- allow force-notification remote-proxy invocations
- eg,
remote.state.update[notification](data)
- also the types for notifications and settings are borked
- eg,