-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Basic SyncManager #132
Conversation
eeb9974
to
2fcec57
Compare
2fcec57
to
fcf661b
Compare
} | ||
} | ||
|
||
#[cfg(test)] |
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.
Nit: move to test dir
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.
no can do sir, this is testing private functionality, needs to be here
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.
I have a nit with tests in source files, especially when we have a test directory. Up to you though.
seperate folders is only for integration tests, unit tests for private variables and functionality have to be within the module, can be in a seperate test file but I thought this was the convention we agreed on |
This branch depends on the header builder pattern #124 so I will just change the base branch to master and open for review once that comes in.I only built out the components that were necessary since this stuff is not defined in the spec and didn't want to assume anything.Wanted to open this up as draft on the off change someone wanted to start any of this.