Separate packages? about coravel HOT 7 CLOSED

Hey @anth12 - thanks for bringing this up. This has been an issue I've been torn on. My original intent was to make Coravel as easy and simple to use - thus, trying to use the least amount of separation possible.

I def. understand that using the scheduler for a micro-service, for example, could work well. But including MailKit... ya I get it.

I'm going to mull over it. Try to keep convincing me while I'm at it lol.

from coravel.

Mailer is separate now. I opted to keep the other features together for now. Just easier for me to maintain and fits better with future plans. Let me know if everything works out or not.

from coravel.

I'm voting this on twitter for a couple days - https://twitter.com/jamesmh_dev/status/1035487034679455744

You can try to get convince people there too ;)

from coravel.

@jamesmh great, I'm glad you are open to the idea. I think having a dedicated package for scheduling in particular would draw a lot more users as its a common requirement. Sure there are other solutions (hangfire, quartz etc.) but they are often quite large & hefty.

I have made a start by refactoring Mail to it's own project.

I get you would like to make it easy to setup everything without worrying about installing x packages, for this I would recommend the approach used by asp.net where they have a .All nuGet which has dependencies on all the various components.

from coravel.

The .All package is a good idea. I wouldn't suggest refactoring it yet since I haven't made any decisions ;)

from coravel.

The mailer is technically already in two packages, so I might just opt to put in the existing one etc. We'll see...

from coravel.

So at the very least I'll be combining the mailer + existing razor page projects into a new one (mailer).

I should be done sometime next week - I'll let you know!

from coravel.