NCronJob-Dev / NCronJob

A Job Scheduler sitting on top of IHostedService in dotnet.
https://docs.ncronjob.dev/
MIT License
158 stars 11 forks source link

v4 #120

Open linkdotnet opened 2 weeks ago

linkdotnet commented 2 weeks ago

This PR will hold all new features for v4. When merged to main - we will release it to the wild. Preview release have to be released from this branch!

Additional (All the features/changes for v4)

This PR includes:

nulltoken commented 2 weeks ago

@linkdotnet What's the plan to reintroduce v3 changes into this branch?

linkdotnet commented 2 weeks ago

I will rebase the v4 with the current master - so we will have all the changes. if there are too many things going on on v4 maybe I’ll switch to merge instead of rebase

nulltoken commented 2 weeks ago

I will rebase the v4 with the current master - so we will have all the changes. if there are too many things going on on v4 maybe I’ll switch to merge instead of rebase

Thx. That'd be helpful. I have started a WIP on the "detection of ambiguous jobDefinitions" (portions of #108 discussion with a v4 target in mind) and I need some portions of #124 (v3) to progress further.

linkdotnet commented 2 weeks ago

I will rebase the v4 with the current master - so we will have all the changes. if there are too many things going on on v4 maybe I’ll switch to merge instead of rebase

Thx. That'd be helpful. I have started a WIP on the "detection of ambiguous jobDefinitions" (portions of #108 discussion with a v4 target in mind) and I need some portions of #124 (v3) to progress further.

I will rebase main after your 2 PR's are merged and hopefully my open one as well :D

nulltoken commented 2 weeks ago

and hopefully my open one as well :D

Yep, I'd also need this one for the ambiguous detection WIP.

linkdotnet commented 2 weeks ago

@nulltoken Rebase done

EDIT: We can also probably "freeze" v3. So that we don't develop any more features. Only if there is a really urgent bugfix, I would argue we should tackle. Otherwise we make our lives harder :D

EDIT 2: That said, your changes should go live, I assume? Therefore I would make a new release.

codecov[bot] commented 2 weeks ago

Codecov Report

Attention: Patch coverage is 94.28571% with 4 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...Job/Configuration/Builder/NCronJobOptionBuilder.cs 72.72% 2 Missing and 1 partial :warning:
src/NCronJob/NCronJobExtensions.cs 95.23% 1 Missing :warning:
Files with missing lines Coverage Δ
...ronJob/Configuration/MissingMethodCalledHandler.cs 100.00% <100.00%> (ø)
src/NCronJob/Registry/IInstantJobRegistry.cs 90.56% <ø> (ø)
src/NCronJob/Registry/JobRegistry.cs 95.87% <100.00%> (+4.66%) :arrow_up:
src/NCronJob/Registry/RuntimeJobRegistry.cs 97.22% <100.00%> (+0.25%) :arrow_up:
src/NCronJob/Scheduler/QueueWorker.cs 70.58% <100.00%> (+6.37%) :arrow_up:
src/NCronJob/NCronJobExtensions.cs 97.36% <95.23%> (-2.64%) :arrow_down:
...Job/Configuration/Builder/NCronJobOptionBuilder.cs 88.28% <72.72%> (+1.88%) :arrow_up:

... and 5 files with indirect coverage changes

nulltoken commented 2 weeks ago

EDIT 2: That said, your changes should go live, I assume? Therefore I would make a new release.

I'd love to be able to benefit from #132 before v4 ;-)

nulltoken commented 2 weeks ago

EDIT: We can also probably "freeze" v3. So that we don't develop any more features. Only if there is a really urgent bugfix, I would argue we should tackle. Otherwise we make our lives harder :D

Deal.

linkdotnet commented 2 weeks ago

EDIT 2: That said, your changes should go live, I assume? Therefore I would make a new release.

I'd love to be able to benefit from #132 before v4 ;-)

Release is on the way