-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provide ember-core from NPM #13022
provide ember-core from NPM #13022
Conversation
How about "ember-core"? I liked @mixonic's "bark" analogy which alludes to Ember as the "core competency" of the Ember ecosystem. As a somewhat tangential comment, I would love to actually see Ember CLI move under the ember repo but released as a separate package. I think this may help with lock stepping projects, overall maintainability, and leverage/integration of tech. A thing working at mega corp has taught me is that for big projects lean towards giant code bases with multiple deployables. |
@chadhietala the reason for an alternative name is to create a meta package named |
For us on the Ember Data subteam, this seems to create an undue burden on core. We have difficulty getting any settings changed because of the various permission levels Github provides. I think ember-cli remaining its own org empowers its subteam to handle their own tools and collaborators, and core can always commit as they are also in that org. |
We should stay in topic. We just need a name for ember-source. So we can reserve ember for a future meta package. |
@stefanpenner In the 2/19 core meeting we seemed to settle on |
☔ The latest upstream changes (presumably #13029) made this pull request unmergeable. Please resolve the merge conflicts. |
@stefanpenner what's the state of this PR? can I help to move this forward? |
Needs a rebase and updating to 'ember-core' as the name. Other than that, I think it's mostly good to land (we can continue to tweak while on master before pushing to NPM). |
rebasing now |
9000502
to
737a034
Compare
@rwjblue updated, i think all the remains is:
Im unsure if this is a blocker, although I can begin working on it over the next few days. (I have small bursts of time) |
@@ -58,6 +57,8 @@ | |||
"ember-cli-path-utils": "^1.0.0", | |||
"ember-cli-string-utils": "^1.0.0", | |||
"ember-cli-test-info": "^1.0.0", | |||
"ember-cli-valid-component-name": "^1.0.0" | |||
"ember-cli-valid-component-name": "^1.0.0", | |||
"simple-dom": "^0.2.7", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did you mean to downgrade this or was this a rebase issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rebase issue, fixing
Rebase thing likely |
@stefanpenner still working on this PR? can I help somehow to bring it over the finish line? |
I'm going to work on it this week, sorry for letting it linger. |
363ba57
to
218a0c4
Compare
Yes, let's target canary. It will branch into beta (for 2.7.0) in a couple days. |
@rwjblue this currently wont actually support canary, as it does not yet work with non-prebuilt versions. Its likely ok as it will hit beta soon. I have some other work, then i'll circle back and make this work on canary, but that will most likely result in a refactoring to emberjs-build etc. |
'default': Ember.inject.controller | ||
}, | ||
'ember-controller/proxy': { | ||
'default': Ember.ArrayProxy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This one felt surprising- ArrayProxy
in the ember-controller
namespace.
Re: ember-cli/ember-cli-shims#60
I guess SortableMixin
is in the same boat. Often used for controllers, but the coupling to the namespace seems odd (if we drop controllers, we will be forced to move/rename ArrayProxy
and SortableMixin
).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In fact ObjectProxy
is just missing re: ember-cli/ember-cli-shims#36. Perhaps we should add a ember-proxy
group 😬
Presented as a checklist so we can check each as "resolved" whether by action or inaction: Three above:
Two others:
|
f8440f3
to
75876e5
Compare
yes, most likely just do this. Coupling this effort to sorting out the public module API has stifled this effort. |
rebased, running tests now. |
Looks like only the blueprint tests are failing (on CI). Taking a look |
also: "DEPRECATION: Overriding init without calling this._super is deprecated. Please call |
Alright, green on this end. At one point this did work end-to-end, it may still? |
I'd say |
Turbo87 someone should try with and without this, and confirm it works. I may have time later this week. If we can make it seamless we have an OK to 🚢 |
@stefanpenner Working with a brand new app and super-rentals. [edit] And a production app of mine. |
bower install ember.js
ember.debug.js, ember.prod.js and
ember-template-compiler.js
on-demand build for master, and maybe beta?can happen afterbackport to release(decided to let it ride the beta cycle so folks can test)related: