Skip to content

add immediate_start to runresponse#33

Open
LachlanJW wants to merge 1 commit into
mainfrom
add-immediate_start-to-runresponse
Open

add immediate_start to runresponse#33
LachlanJW wants to merge 1 commit into
mainfrom
add-immediate_start-to-runresponse

Conversation

@LachlanJW

@LachlanJW LachlanJW commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

This allows UI to filter playlists in a much simpler way, currently there is a fragile hardcoded list of immediate start tests, this sends the info from orchestrator. Once this is ready update orchestrator to new pin. PR is ready for it.

@LachlanJW LachlanJW requested a review from joshvote June 18, 2026 04:57
@joshvote

Copy link
Copy Markdown
Contributor

✅ Code coverage on add-immediate_start-to-runresponse is at 100% (compared to main being at 100%)

🎉 No files have reduced coverage 🎉

Full Coverage Report

File Details
src/cactus_schema/__init__.py ✅ 100% → 100%
src/cactus_schema/notification/__init__.py ✅ 100% → 100%
src/cactus_schema/notification/schema.py ✅ 100% → 100%
src/cactus_schema/notification/uri.py ✅ 100% → 100%
src/cactus_schema/orchestrator/__init__.py ✅ 100% → 100%
src/cactus_schema/orchestrator/compliance.py ✅ 100% → 100%
src/cactus_schema/orchestrator/schema.py ✅ 100% → 100%
src/cactus_schema/orchestrator/uri.py ✅ 100% → 100%
src/cactus_schema/runner/__init__.py ✅ 100% → 100%
src/cactus_schema/runner/schema.py ✅ 100% → 100%
src/cactus_schema/runner/uri.py ✅ 100% → 100%
TOTAL ✅ 100% → 100%

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