refactor: remove ipc override from options and give it manually to test #2629
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If I understand correctly, creating the IPC backend from a "string" will not be easily possible, and the types used are not serializable or cloneable.
I envision a future were we can override build backends selectively, and so it would be good to be able to use a hash map such as:
But to achieve this, we need a type that is easier to use than the current Io backend. Since that backend override is only used in testing, we can use more direct methods of setting it in the Protocol.
Lmk what you think @tdejager / @baszalmstra