feat(5326): Combining destructuring with parameter properties

[a-tarasyuk]

Fixes #5326

Accepting PRs to implement constructor(public {name1, name2}) forms (i.e. no public / private etc inside the {}s).
#5326 (comment), #5326 (comment)

[ianldgs]

I understand that this is how @RyanCavanaugh "approved" this feature to be implemented, but that was a long time ago. Paradigms have changed: nowadays, immutability is a much hotter topic than in the past when getters/setters and encapsulation were the most accepted concept for class properties.

If TypeScript goes towards this direction, I don't see a way to extend this feature to represent:
1: readonly fields and 2: together with public, some fields that are private and some maybe even protected.

Any thoughts?

In any case, @a-tarasyuk I really appreciate someone taking the initiative to start the work on this, let me know if I can also contribute!

[typescript-bot]

The TypeScript team hasn't accepted the linked issue #5326. If you can get it accepted, this PR will have a better chance of being reviewed.

[a-tarasyuk]

@ianldgs I think it would be better to post your comment on #5326 to continue the discussion there. This PR will not be merged, I'll later reset the changes and close the PR.

[sandersn]

@a-tarasyuk it sounds like you're going to abandon this PR?

I have to say that we're not excited about doing work on parameter properties, since they're not ES standard. So it might be the right thing.

[a-tarasyuk]

@sandersn closed. I think that the label Help Wanted should be changed to In Discussion/Awaiting More Feedback.