GitHub user marvin-hansen added a comment to the discussion: SDK crate split & new crate structue
For now, the proposed crates are: * iggy_error * iggy_types (type and trait definition used in server and SDK) * iggy_common (most likely contains functionality, serialization, and utils shared in server and SDK) * iggy_protocol (The binary protocol and its default implementation) I tend to separate types from errors mainly to re-used errors in all sorts of crates without a long tail of unrelated deps. I think that also helps to clean up the server errors by simply creating maybe 2-3 error crates to fully isolate errors by domain, add unit testing and call it a day. Any other ideas or thoughts? GitHub link: https://github.com/apache/iggy/discussions/1734#discussioncomment-13029127 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
