Skip to content

Conversation

@buck54321
Copy link
Member

This is just a small architectural change that elevates the order maps from dexConnection to Core in preparation for integrating mesh as a source of trades. I think this will save us some headaches going forward.

Copy link
Collaborator

@martonp martonp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reasoning behind this? My inclination would be to go in the opposite direction. Instead of bringing things from dexConnection into core, I think it would make more sense to keep things in dexConnection and not have core know about the internal details of dexConnection. The dexConnection type should be turned into an interface that both meshConnection and v1DexConnection (or whatever it's called) implement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants