Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

Issues: tc39/proposal-class-fields

36 Open 208 Closed
36 Open 208 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Please Don't Do That.
#331 opened Jun 5, 2021 by luciedefraiteur
8
Proxy nested inside of the Prototype Chain
#330 opened Apr 19, 2021 by wentout
2
Statement of our opinions on class fields and its related package of proposals
#329 opened Apr 19, 2021 by zeldajay
2
Why are #private fields not source-positional?
#328 opened Apr 16, 2021 by trusktr
22
Properties without initializers can create some headache in "real-world" scenarios.
#323 opened Oct 1, 2020 by dfahlander
14
[[Define]] semantics necessitate workarounds
#322 opened Sep 30, 2020 by trusktr
7
Class composition
#319 opened Sep 2, 2020 by rowaasr13
3
Support for privates in object literals?
#318 opened Aug 25, 2020 by dgkimpton
3
[Suggestion] Consider to use time proof solution with private and protected keywords
#315 opened Aug 4, 2020 by redradist
39
Motivation for PrivateFieldAdd type error? documentation
#308 opened May 12, 2020 by mgaudet
5
Why a new LexicalEnvironment Parameter? editorial
#306 opened Apr 24, 2020 by mgaudet
10
Execution of initializer expressions is confusing in readme documentation
#299 opened Mar 5, 2020 by papb
How to fix this proposal's inheritance issues
#276 opened Oct 16, 2019 by rdking
Could we have avoided "fields"?
#274 opened Oct 6, 2019 by rdking
39
Insufficient time allotted for acceptance testing [[Define]] semantics
#273 opened Oct 4, 2019 by rdking
5
Assigning a function to a private field isn't ideal
#270 opened Sep 14, 2019 by puppy0cam
14
A new proposal, maybe late maybe not.
#264 opened Aug 21, 2019 by aimingoo
55
How to dynamically access private properties/classes
#257 opened Jul 18, 2019 by d42ohpaz
26
The argument against this proposal
#255 opened Jul 8, 2019 by rdking
23
Do not hesitate to make design changes just because Chrome has shipped
#254 opened Jul 1, 2019 by jhpratt
9
Treating the # as part of a .# operator instead of as part of a field name #foo.
#250 opened Jun 26, 2019 by trusktr
39
Use [[Set]] by default, add define keyword. (was: TypeScript class fields have [[Set]] semantics.)
#248 opened Jun 17, 2019 by trusktr
36
Honour class property values set by parents
#242 opened May 30, 2019 by brianmhunt
51
Private member access from static methods documentation
#239 opened May 20, 2019 by rijnhard
5
Early Error rules need to be referenced explicitly in PerformEval
#234 opened Apr 12, 2019 by jorendorff
1
ProTip! Updated in the last three days: updated:>2024-11-20.