-
Notifications
You must be signed in to change notification settings - Fork 632
[CDEC-432] Move Mockable
and JsonLog
to core
#3238
Conversation
|
||
|
||
|
||
|
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.
Wow, that is a lot of empty lines. Is that just the way it was in the original file?
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.
It seems that was indeed the case. Weird!
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.
Yep 🤷♂️ In the spirit of minimal changes I left it. But several of these modules definitely could use tidying up.
As you can see from the dependency graph, the This is why there is also networking code in We do it like this so the transition happens in a number of smaller PRs that are easier to review (this one is by far the worst). It should also be noted that the dependency graph above is about a week out-of-date and that |
These modules were previously in `networking`, which caused a dependency from `core` on `networking`. In an effort to free up `networking` (so that it can move up in the dep graph), we move those 2 modules into `core`. Several of the moved modules relied on an implicit prelude in `networking`. Since `core` has NoImplicitPrelude in its `default-extensions`, we had to add `import Prelude`. We also re-export `JsonLog` & `Mockable` from `networking`.
50ef0e1
to
0aeeae9
Compare
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.
Description
Move
Mockable
andJsonLog
into core, so that networking can be freed up. The goal is to letnetworking
float upwards in the dependency graph.Linked issue
https://iohk.myjetbrains.com/youtrack/issue/CDEC-432
Type of change
Developer checklist
Testing checklist
^ this PR moves code around & doesn't change functionality. Existing tests should be good enough.