Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Class field breaking change mitigation strategy #29580

Closed
RyanCavanaugh opened this issue Jan 25, 2019 · 2 comments
Closed

Class field breaking change mitigation strategy #29580

RyanCavanaugh opened this issue Jan 25, 2019 · 2 comments
Assignees
@RyanCavanaugh
Labels
Duplicate An existing issue was already created

Comments

@RyanCavanaugh
Copy link
Member

(TBD)
@RyanCavanaugh RyanCavanaugh added the Breaking Change Would introduce errors in existing code label Jan 25, 2019
@RyanCavanaugh RyanCavanaugh self-assigned this Jan 25, 2019
@sandersn
Copy link
Member

Related: JS should now allow property declarations: #27023.

We'll need to think about any semantic differences between JS and TS.

@RyanCavanaugh
Copy link
Member Author

Duplicate #27644

@RyanCavanaugh RyanCavanaugh added Duplicate An existing issue was already created and removed Breaking Change Would introduce errors in existing code labels Jan 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RyanCavanaugh RyanCavanaugh

Labels
Duplicate An existing issue was already created
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sandersn @RyanCavanaugh