Experimental support for class fields

[jugglinmike]

The "public class fields" proposal is currently at stage 2 in the TC39 standardization process. In accordance with our policy on new language features, we should implement support for this on an experimental basis.

Edited to add: the language proposal is now maintained as "class fields", and it has reached stage 3.

[sSeewald]

Any updates on that? It's stage 3 now.

[andrewvaughan]

Can this be reviewed, please?

[jugglinmike]

@andrewvaughan This isn't a pull request, so there's no code to review. We've been ready to accept patches for it since I opened the issue, so we don't need to revisit policy, either. All that's needed is for someone to write the code. Might that be you?

[jugglinmike]

I'd be happy to help you get your bearings, of course!

[andrewvaughan]

@andrewvaughan This isn't a pull request, so there's no code to review. We've been ready to accept patches for it since I opened the issue, so we don't need to revisit policy, either. All that's needed is for someone to write the code. Might that be you?

Normally I'd be happy to contribute - but, until very recently, JSHint was still functioning in the ES6 realm, which was surpassed nearly three years ago. Given that ES7, 8 and 9 were all supported in a giant patch just a few days ago, I'm not filled with tremendous faith that the project will remain current and my work would be beneficial.

If it were released more incrementally and in-line with the EMCA revisions, I'd be inclined to, but at this point, it makes more sense to strip JSHint from my project and use another linting tool in the meantime.

Best of luck with the project.

[jugglinmike]

The "public class fields" proposal has been merged with one for private class fields. I've updated this feature request's title accordingly.

[TheBrenny]

Pre: Sorry to bump everyone watching this.

But is there a more detailed update on this being "implemented"? This issue is looking like JSHint is tracking that a change is coming, but is there any progress on it's implementation? Even a Status: waiting on _____ message would be nice! Is there maybe a place where we can go to create a workaround or a branch that has this implemented ready to be merged that we can pull?

I just want VSCode to stop yelling at me when I want to make private fields in my classes. 🥺👉👈

[jugglinmike]

No updates. We use GitHub.com exclusively for coordination, so if there are any developments, this issue is the place to look!