Closed toddb closed 1 year ago
My vote is to take the hit now and release them separately allowing for people to have as few a dependencies to allow for those that have different environments and minimal requirements.
However, another way to merge Extensions back into Core and only release two packages. But Core then has dependencies on Microsoft around DI and Configuration—any business software will have this (IMHO). Much of the extensions code are utility helpers that live as extension methods which are not technically extensions but extension methods.
I too agree that we change the packaing to the following:
Novu.Extensions
projectNovu.Sync
projectIf we take the hit now, it will be better going forward.
@unicodeveloper thoughts?
I'll take this one and get it out in #61
Released 0.3.1
Novu has three parts/dlls:
Refit
as the primary across-the-wire client—not necessarily the http client (and Json.net)—future warning that this library is now bound to the dependency upgrade policies of Refit (for example))There is a decision:
The code as part of 0.3.0 did not release this code.
Note: Novu may need to be called Novu.Core (or the like) indicating base.