Skip to content
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

Split out implementation and interfaces into a separate packages #5

Open
tugberkugurlu opened this issue Jan 4, 2019 · 2 comments
Open

Comments

@tugberkugurlu
Copy link

It would be great to have a separate package for Interfaces (e.g. Redbus.Abstractions). The main need I have for this is that I want my domain project to have a reference to Redbus.Abstractions package but don't want it to have a reference to concrete implementation of the event bus so that it prevents direct coupling to the implementation.

I am happy to contribute this but wanted to check with you first to see if this would be something you are up to having.

@tugberkugurlu tugberkugurlu changed the title Split out interfaces into a separate package Split out implementation and interfaces into a separate packages Jan 4, 2019
@mxjones
Copy link
Owner

mxjones commented Jan 10, 2019

@tugberkugurlu yes that sounds good to me 👍 - You can go ahead with the changes neccessary for this if you want and submit a PR and I will sort out the NuGet package related stuff, thanks!

@facundofarias
Copy link

True @tugberkugurlu! Same happening here!

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

No branches or pull requests

3 participants