Concerns over this library about ember-cli-shims HOT 4 CLOSED

I thought things landed on @stefanpenner proposing the use of @ember/object.

Ya, I'm not sure why this path wasn't taken. I would still prefer it.

As per learning/docs. I suspect the docs will evolve once the dust settles on module signature.

The nice thing though, is any modules are better then none. And the static nature of them, means if we decide to transition to another format. An automated tool could very accurately make the transition in one swoop.

cc @locks as he may have some learnings ideas.

from ember-cli-shims.

re: @ember/foo

is there an opportunity to change the syntax of the modules in the library? Last I recall everyone was on board with that style

from ember-cli-shims.

Last I recall everyone was on board with that style

Was this the case, i seem to remember push-back. I of-course am biased, and prefer the @ember/foo pattern.

Ultimately no hasty changes will be made, but the above comments are useful.

emberjs/rfcs#68 hasn't been merged, which means it hasn't been finalized. So continuing this discussion there might be appropriate. emberjs/rfcs#68

from ember-cli-shims.

closing this as emberjs/rfcs#176 has replaced emberjs/rfcs#68 and essentially deprecated this project

from ember-cli-shims.