Revert "eslint(container-runtime): Prefix container-runtime before enabling no-unchecked-record-access" #23499
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.
Reverts #23437
Where
?
was used to address linter defect, TypeScript appears to mostly ignore that these cases may lead toundefined
result which is not accepted per type specifications. Use of?
is thus a behavior change that will shift point of failure away from where it could first be detected - revert those behavior changes. (Many of the test uses of?
in original change are permissible as there is a follow-up assertion that will fail. But those were not separated during revert.)Where
T | undefined
was used to address linter defect, TypeScript will narrow withoutundefined
withoutnoUncheckedIndexAccess
enabled. Thus, the code appears more confusing as there is a non-respected type annotation.