Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v4 #120

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

v4 #120

wants to merge 8 commits into from

Conversation

linkdotnet
Copy link
Member

@linkdotnet linkdotnet commented Nov 1, 2024

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:

@linkdotnet linkdotnet force-pushed the v4 branch 2 times, most recently from d7ac3a9 to 8526904 Compare November 3, 2024 09:44
@nulltoken
Copy link
Collaborator

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

@linkdotnet
Copy link
Member Author

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
Copy link
Collaborator

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
Copy link
Member Author

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
Copy link
Collaborator

and hopefully my open one as well :D

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

@linkdotnet
Copy link
Member Author

linkdotnet commented Nov 4, 2024

@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.

Copy link

codecov bot commented Nov 4, 2024

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 ⚠️
src/NCronJob/NCronJobExtensions.cs 95.23% 1 Missing ⚠️
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%) ⬆️
src/NCronJob/Registry/RuntimeJobRegistry.cs 97.22% <100.00%> (+0.25%) ⬆️
src/NCronJob/Scheduler/QueueWorker.cs 70.58% <100.00%> (+6.37%) ⬆️
src/NCronJob/NCronJobExtensions.cs 97.36% <95.23%> (-2.64%) ⬇️
...Job/Configuration/Builder/NCronJobOptionBuilder.cs 88.28% <72.72%> (+1.88%) ⬆️

... and 5 files with indirect coverage changes

@linkdotnet linkdotnet changed the title v4 work v4 Nov 4, 2024
@nulltoken
Copy link
Collaborator

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
Copy link
Collaborator

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
Copy link
Member Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants