-
Notifications
You must be signed in to change notification settings - Fork 81
refactor&more (feel free to review, still improving docs and tests) #159
Conversation
still going down the refactoring rabbit hole ; ) lots of local changes still to be committed and pushed. though the end is in sight and i'm much more comfortable with the codebase |
almost done here. i'll give my go when all grumbles are fully addressed |
main_to_side_sign: RelayStream<LogStream<T>, main_to_side_sign::LogToMainToSideSign<T>>, | ||
side_to_main_sign: RelayStream<LogStream<T>, side_to_main_sign::LogToSideToMainSign<T>>, | ||
side_to_main_signatures: | ||
RelayStream<LogStream<T>, side_to_main_signatures::LogToSideToMainSignatures<T>>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be in the new line
pub contract: ContractConfig, | ||
pub ipc: PathBuf, | ||
pub http: String, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can this be configurable? ipc or http?
} | ||
|
||
/// extends the `Stream` trait by the `last` function | ||
pub trait StreamExt<I> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it used only in tests? if so, can you move it to cfg(test)
?
let's get it in and resolve other issues separately |
side to main sign, side to main submit signatures) into
RelayStream
RelayStream
for any process that listens to aLogStream
and executes transactions for each log
home
/foreign
tomain
/side
as the previous namingtended to confuse most people
Config
andDatabase
MainContract
andSideContract
highlevel interfaces that are used by relay streams instead of scattering that logic throughout the relay streamsApp
abstraction