PENDING:
- auto message ids
- docs for services
- Test kit docs
- Api ref docs
- Tests
- Test overlap in console output manually tested
- Test resource safety in callbackRegistry manually tested
- Automated tests
- Out messages should not need to define types. Use class name. May need to use macros
TBD:
- Create Maelstrom node parent class
- Assess importance
- Multiple request-response can be started. There should be only one handler for a node
- Not a V1 requirement
- User messages should not be restricted to a msg_id of Int
- Is it worth the complexity?
- If a message is awaited, and another callback is is being registered with same messages id from same remote, then it results in unintended behavior
- Does this need to be solved in this library?
DONE:
- Error code hierarchy needs to be simplified
- File input is not working
- Make internal types/apis private
- Add concurrency in settings
- Ask pattern
- Use intersection types for message hierarchy. IN messages don't need "type"
- Separate init from receive messages
- Create documentation
- Add more examples
- Test kit
- Fix the dam blinking debug messages