nulltoken
nulltoken
#215 introduced a branch in the fluent interface for the sake of backward compatibility. It also put under the light an issue with the current design which allows `.WithParameter().WithParameter()` chaining...
It's allowed to call `AddNCronJob()` multiple times. To be effective, some consistency checks will require that all initial registrations are done. The proper place to run them would be through...
Currently registering those two kind of jobs is done through very different interfaces ``` builder.AddJob(p => p.WithCronExpression("* * * * *").WithName("MyName")); ``` vs ``` builder.Services.AddNCronJob(b => b.AddJob(() => {}, "*...
Currently we've got things like this ``` public void RemoveJob() where TJob : IJob => RemoveJob(typeof(TJob)); public void RemoveJob(Type type) => jobWorker.RemoveJobByType(type); ``` and others than only expose generic based...
Observability brought the concept of Orchestration to identify a root job and all the hierarchy of its dependent jobs. CorrelationId was existing before but fit exactly the concept of the...
Although V4 is not done yet, this placeholder is a proposal to hold discussions about things that may need to be changed but would induce a breaking change
Although not a pure breaking change, this may require some deep rework that would be made easier would we decide to get rid of `IJobNotificationHandler`
I'm not really seeing the value of this anymore. Given that - `IExceptionHandler` already handles exceptions - Some minor improvements to `IJobExecutionProgressReporter` may allow a client to register to filtered...