nulltoken

>I guess I do have an idea for fix: I was also toying with something on my side. We currently link by Job type. Now that all the interesting pieces...

>Basically: A job that does get triggered directly. Still, at least that is my assumption, dependent jobs, should be executed. Of course we could also argue, that isn't part of...

Considering most of those are edge cases and as of now everything lives in the JobRegistry, there could be a path where the lib would analyze the trees of potential...

FWIW, it's not a "production" issue on my side. Just one thing I've stumbled upon while working on #106. Once JobRegistry was assembled, this typed based approach downside somehow raised...

Reopened as only partially addressed through #124

A follow up on https://github.com/NCronJob-Dev/NCronJob/issues/128#issuecomment-2453571205 which belongs more to this issue: The context of dependent jobs should not be considered in the scope of `AddNCronJob()` only, but also with the...

@linkdotnet Here's a first batch of things to ponder about. Each of them in a separate sub-issue to be able to focus the exchanges per topic and potentially ditch it...

> If we start working on `v5` I would put `v4` into maintenance because otherwise, it leads to waste. I'd suggest to keep v4 open for now. I believe there...

@linkdotnet Not all tests are passing. Before going further with how the code should be changed to make them pass, I'd like some feedback from you about the following points:...

@ThisIsMissEm Thanks a lot for this feedback. Sadly, I'm not as well versed in RFCs than @poveden is. So you might need to help me a bit out in order...