Decorators aren't ES2016/ES7 but people seem to think they are
Closed this issue · 1 comments
Because the decorators proposal pre-dates the change from ES6/ES7 to ES2015, ES2016, etc (yearly dated-based) and just general misunderstanding of how the new spec process works, many people erroneously know decorators as "ES7 decorators" or less common "ES2016 decorators" even though they did not make the cut for 2016.
The problem we have now is that if we remove these terms from the repo description, README, etc people might have a harder time finding this project and/or possibly not realizing what it is or that it's not a feature officially supported by any final spec.
That said, I would like to stop reinforcing these incorrect terms so I still say we remove them. Any objections?
Added additional clarification to the README.