feat(container-runtime): allow createBlobPayloadPending to be explicitly set to false - #28097
feat(container-runtime): allow createBlobPayloadPending to be explicitly set to false#28097Daniel Madrid (dannimad) wants to merge 1 commit into
Conversation
- Widen createBlobPayloadPending option type from true|undefined to boolean|undefined in IContainerRuntimeOptionsInternal. - Include false in the test-service-load options matrix for pairwise coverage. - Acknowledge the resulting backCompat type-test breaks in container-runtime and aqueduct package.json, and regenerate the affected type test files. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Copilot reviewed 10 out of 10 changed files in this pull request and generated no comments.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
🔗 Found some broken links! 💔 Run a link check locally to find them. See Checking for Broken Links for more information. linkcheck output |
|
Hi! Thank you for opening this PR. Want me to review it? Based on the diff (40 lines, 10 files), I've queued these reviewers:
How this works
|
|
I think this sounds like it's probably part of what needs to happen, but I'd really like to see that plan of "here's how a vanilla feature uses document schema to ship" first, so we can confirm that any changes to this feature are "just aligning to the normal plan". Just because it's so hard to undo any changes in this space if we realize a different approach is preferable. |
Bundle size comparisonBase commit: Notable changesNo bundles changed by ≥ 500 bytes parsed. Per-bundle deltas
|
Description
createBlobPayloadPendingonContainerRuntimeOptionspreviously only acceptedtrue | undefined. This widens the type toboolean | undefined, so consumers can explicitly passfalseto disable the feature (equivalent to leaving itundefined). Also addedfalseas an explicit option in the test-service-load pairwise options matrix for coverage.This is a non-breaking, backwards-compatible widening of the accepted values at runtime. It does trip the generated backCompat type tests (a narrower type is no longer assignable to the widened type), which have been acknowledged in
container-runtime's andaqueduct'spackage.json(typeValidation.broken), and the corresponding type test files were regenerated.Reviewer Guidance
The review process is outlined in the pull request guidelines.
typeValidation.brokenentries incontainer-runtime/package.jsonandaqueduct/package.jsonlook correct.