Skip to content

Spike: Investigate breaking type changes #3321

@redallen

Description

@redallen

Introducing types at all is technically a breaking change for Typescript consumers. Yet, I don't think Typescript consumers were too upset with us when we introduced types for component properties because that gave them a compile-time check for their props.

But now comes Phase 2: supporting and modifying these types where we were previously incorrect or previously used any. How we should introduce this to consumers without breaking their compile-time check for their props? It's not good for our types to stay incorrect. It's also not good to break Typescript consumers from one minor version to the next.

I think something that will ease or pain is an official types package and looking at how other libraries manage their types between releases. I'm sure it can quickly get complicated, so I think it deserves an investigation.

Related: #3296

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions