[typescript-operations] Handle printing types consistently when types are any and unknown
#10574
+75
−29
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.
Description
When a TypeScript type is
anyandunknown, and we try to add other union options e.g.any | null | undefined, they'd be collapsed down to theanyorunknown.This PR adds
printTypeScriptTypeto consistently print TypeScript types with these scenarios in mind.Note: this function doesn't exhaustively does all scenarios right now (maybe it shouldn't, otherwise, it'd be too many cases? 🤔 ). Anyways, adding it here for consistency and we can see how it evoles.
Related #10496
Type of change
Please delete options that are not relevant.