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

fix: Make jobs property fully optional in the cronjob endowment #3005

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

FrederikBolding
Copy link
Member

Make the jobs property fully optional in the cronjob endowment since it is also allowed to be empty.

We accounted for and discussed this in #2941, but must have forgotten to allow endowment:cronjob: {}.

@FrederikBolding FrederikBolding requested a review from a team as a code owner January 10, 2025 13:25
@FrederikBolding FrederikBolding force-pushed the fb/make-cronjobs-fully-optional branch from 1fd8ce1 to 7525e12 Compare January 10, 2025 13:25
Copy link

codecov bot commented Jan 10, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.72%. Comparing base (497b10f) to head (7525e12).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3005   +/-   ##
=======================================
  Coverage   94.72%   94.72%           
=======================================
  Files         497      497           
  Lines       10826    10826           
  Branches     1654     1654           
=======================================
  Hits        10255    10255           
  Misses        571      571           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@FrederikBolding FrederikBolding merged commit 399dbee into main Jan 10, 2025
166 checks passed
@FrederikBolding FrederikBolding deleted the fb/make-cronjobs-fully-optional branch January 10, 2025 13:38
PatrykLucka pushed a commit that referenced this pull request Jan 13, 2025
)

Make the `jobs` property fully optional in the cronjob endowment since
it is also allowed to be empty.

We accounted for and discussed this in #2941, but must have forgotten to
allow `endowment:cronjob: {}`.
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