fix: update DeleteWorkspaceOptions
to pick properties correctly
#13423
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.
Found this while writing the docs for the Backstage Coder SDK:
It's literally a single character difference, but the second
Pick
argument should be:Changes made
&
to a|
Explanation
With the
&
, you have an intersection instead of a union. Basically, that says "give me a type that is both the literal"log_level"
and the literal"orphan"
at the same time". It's impossible for a value to be two different things at the exact same time, so the resulting type isnever
. When you picknever
from an object, you pick nothing, so the ultimate resulting type is the type{}
(which is equivalent toNonullable<unknown>
).Nonullable<unknown>
isn't much better than anany
type – it's basicallyany
, but withnull
andundefined
removed