Skip to content

RFC: New name for strictOptionalProperties #44604

Closed
@RyanCavanaugh

Description

@RyanCavanaugh

Per discussion at #44421 and #44524, we're moving the flag currently named strictOptionalProperties out of the strict family and into the off-by-default category inhabited by other options like noImplicitReturns, noUncheckedIndexedAccess, and allowUmdGlobalAccess

As such, we need a new name for this. As a refresher, the flag makes it so that a property that is optional, e.g. { x?: string }, cannot be initialized with the actual value undefined, e.g. someObj.x = undefined. If this flag is not set, then today's behavior of allowing undefined values to be assigned into optional properties remains. There is no effect on parameters.

Please only post name suggestions (one per comment) and votes; actual discussion on the flag should remain at #44421. Happy coding!

Metadata

Metadata

Assignees

No one assigned

    Labels

    DiscussionIssues which may not have code impact

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions