include Reflect es7 metadata

[PatrickJS]

it would be great for angular2 if we only had to include core-js rather than es6-shim, es6-promise, and reflect-metadata
https://github.com/rbuckton/ReflectDecorators

[zloirock]

I think about it a few months. The problem here - it's not an official ES proposal. It's very simple for implementation, so I think makes sense add it as an experimental feature. Or wait for the next TC39 meeting - IIRC decorator proposal should be updated.

[PatrickJS]

would it be too crazy to ask for an experimental folder path so all Angular 2 developer could rejoice
from

import 'es6-shim';
import 'es6-promise';
import 'es7-reflect-metadata/dist/browser';
import 'zone.js/lib/browser/zone-microtask';
import 'zone.js/lib/browser/long-stack-trace-zone';

to

import 'core-js/experimental';
import 'zone.js/lib/browser/zone-microtask';
import 'zone.js/lib/browser/long-stack-trace-zone';

then we only need to update zone.js

import 'core-js/experimental';
import 'zone.js/lib/browser/zone-microtask';

which could live in

import 'angular2/polyfills';

[zloirock]

cc @wycats @rbuckton what do you think about it? Any conflicts with changes in the decorators proposal? Perspectives as an official proposal?

[PatrickJS]

thanks for adding it as experimental 👍

[zloirock]

@gdi2290 currently, I just play with it and explore possibilities. I think it can be added in the next minor release.

[zloirock]

I can add it right now as a pre-strawman feature (in this case it can be available not only in the 'core-js' entry point - also in 'core-js/shim' -> 'babel-polyfill'), but some problems confuse me:

• Reflect.decorate missed in the spec text, but available in rbuckton/ReflectDecorators.
• Fallback for GetPrototypeOf in rbuckton/ReflectDecorators for non-spec-compliant TypeScript (or Babel with proto-to-assign) classes. Sure, I can add the same fallback, but I don't think it's a good idea - inherited metadata will not work with constructors and statics if it will be implemented natively.
• I don't see any feedback here or in the repo with the spec text from champions. Is this proposal alive? One more time: cc @wycats @rbuckton

[zloirock]

Ok. In the next minor version (2.1) - after some days - it will be enabled by default. If current implementation will cause any problems - it's already not my problems. The questions above, I don't see any answers.

[PatrickJS]

thanks