You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JobDefinition and JobDefinitionRecord duplicated the same configuration and required startup to copy every field between them. Remove JobDefinitionRecord and use JobDefinition across scheduling, storage, monitoring, testing, and the dashboard client. Startup now registers definitions directly.
Queue settings live solely on Queue: consumers use its Name, Priority, and Concurrency, with no corresponding aliases on JobDefinition. Dashboard payloads and newly written Redis metadata use a nested queue object. SQL storage keeps the existing column mappings, and Redis readers and Lua scripts support previously stored flat metadata. Local invoker and CLR type bindings are optional and excluded from serialization, along with computed acquisition limits.
Validation:
Functional and storage projects build on .NET 8, 10, and 11 with warnings treated as errors; zero warnings or errors.
155 functional tests pass on each framework.
658 storage tests pass on each framework, covering SQLite with EF Core and LinqToDB, in-memory and capturing storage, live Redis, serialization, and conformance infrastructure. Regression coverage includes acquiring jobs from old Redis metadata and updating the catalogue to nested queue settings.
Dashboard lint, type checks, all 61 client tests, production build, and bundle size check pass.
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
📝 Walkthrough
JobDefinition now serves as the shared definition type for execution, storage, and monitoring. Queue settings serialize as flat fields, while runtime bindings and computed acquisition limits are excluded. Storage and dashboard contracts use the updated type, and execution checks for a missing invoker.
Changes: Shared job definition
Layer / File(s)
Summary
Definition model and JSON shape src/Immediate.Jobs.Shared/Internals/JobDefinition.cs, src/Immediate.Jobs.Shared/Apis/JobDefinitionRecord.cs, tests/Immediate.Jobs.StorageTests/JobDefinitionSerializationTests.cs, docs/architecture.md
JobDefinition replaces the removed JobDefinitionRecord. Queue settings use flat JSON fields, while runtime bindings and computed acquisition limits are omitted. Serialization tests cover round trips and existing flat metadata.
Storage interfaces, in-memory storage, and EF Core, LinqToDB, and Redis implementations now use JobDefinition. Scheduling passes definitions directly to storage. Execution paths throw InvalidOperationException with the job name when the invoker is missing. Related storage tests and test doubles use the updated type.
Monitoring and dashboard contracts src/Immediate.Jobs.Shared/Apis/JobMonitoringDefinitions.cs, src/Immediate.Jobs.Dashboard/DashboardJsonSerializerContext.cs, src/Immediate.Jobs.Dashboard/DashboardClient/src/contracts.ts, src/Immediate.Jobs.Dashboard/DashboardClient/src/query.ts, src/Immediate.Jobs.Dashboard/DashboardClient/src/components/JobDetail.vue, tests/Immediate.Jobs.FunctionalTests/Packages/DashboardPackageTests.cs
Monitoring and dashboard contracts use JobDefinition. The dashboard API test checks for queueName and verifies that queue, invoker, jobType, and acquisitionLimits are absent.
No actionable merge-blocking issue is established for this change; it is mergeable after normal checks.
Pre-merge checks: 4 · 1
Failed checks: 1 warning
Check name
Status
Explanation
Resolution
Docstring Coverage
Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 72 functions across 35 files. (2 skipped:…
Write docstrings for the functions missing them to satisfy the coverage threshold.
Passed checks: 4 passed
Check name
Status
Explanation
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title is concise, specific, and accurately describes the primary change: removing the redundant JobDefinitionRecord type.
Full details: Docstring Coverage
Explanation
Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 72 functions across 35 files. (2 skipped: 2 unsupported.)
Resolution
Write docstrings for the functions missing them to satisfy the coverage threshold.
Fix all pre-merge checks with AI
✨ Finishing Touches: 💡 2
📝 Generate docstrings: 💡
Commit to this branch
Create a new PR
🛠️ Fix failing CI checks: 💡
Commit to this branch
Create a new PR
🧪 Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JobDefinitionandJobDefinitionRecordduplicated the same configuration and required startup to copy every field between them. RemoveJobDefinitionRecordand useJobDefinitionacross scheduling, storage, monitoring, testing, and the dashboard client. Startup now registers definitions directly.Queue settings live solely on
Queue: consumers use itsName,Priority, andConcurrency, with no corresponding aliases onJobDefinition. Dashboard payloads and newly written Redis metadata use a nested queue object. SQL storage keeps the existing column mappings, and Redis readers and Lua scripts support previously stored flat metadata. Local invoker and CLR type bindings are optional and excluded from serialization, along with computed acquisition limits.Validation: