Migrate code to ES6 classes
Reported by
noj...@gmail.com,
Jul 7 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: There's quite a lot of code in devtools front end using prototype inheritance. Now that v8 officially supports most of ES6, it would make sense to migrate to class based code rather than prototype inheritance based code. Also wondering if the devtools team has give any thought on using typescript? What is the expected behavior? What went wrong? Would be nice to have DevTools front end code update to modern javascript style. Did this work before? N/A Chrome version: 51.0.2704.103 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0
,
Jul 7 2016
We never prioritized the classes due to no immediate benefit. But we are open to the patches in case you are interested in doing it. As for the TypeScript, we want to implement / migrate a couple of modules to the TypeScript to ensure that we have enough frameworks dogfooding. At this point, we are lacking CI capabilities for that (no Node running on the Chromium build bots). It is also important that most of our code is based on the raw web platform.
,
Jul 29 2016
Let us reopen this when we see PRs that are doing this. |
|||
►
Sign in to add a comment |
|||
Comment 1 by noj...@gmail.com
, Jul 7 2016