Skip to content
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

Ember 3.0 Related Cleanup #15876

Closed
31 of 34 tasks
rwjblue opened this issue Nov 29, 2017 · 32 comments
Closed
31 of 34 tasks

Ember 3.0 Related Cleanup #15876

rwjblue opened this issue Nov 29, 2017 · 32 comments

Comments

@rwjblue
Copy link
Member

rwjblue commented Nov 29, 2017


To pick up one of these items, please comment below and we'll update the checklist with :lock: @your-name-here...

@sivakumar-kailasam
Copy link
Member

@rwjblue Should Ember.WeakMap be removed too?

@rwjblue
Copy link
Member Author

rwjblue commented Nov 29, 2017

@rwjblue Should Ember.WeakMap be removed too?

I believe it is on the list above, under Remove 'packages/ember-metal/lib/weak_map.js'

@thoov
Copy link
Member

thoov commented Nov 29, 2017

If they haven't been taken I can start off with working on the Leverage native WeakMaps and all of the sub tasks for this

@rwjblue
Copy link
Member Author

rwjblue commented Nov 29, 2017

@thoov - Some are being tackled by @sivakumar-kailasam in #15878, can you take a look at that PR to help review (and determine what I've missed...)?

@thoov
Copy link
Member

thoov commented Nov 29, 2017

@rwjblue I will help with the review of that. I will change up my tactic and take the bottom 4 off of the list then.

@rwjblue
Copy link
Member Author

rwjblue commented Nov 29, 2017

@thoov - Sounds good! I have updated the items and marked the whole Deprecations subsection as 🔒ed, because we will need to create the legacy support addon and ENV flag infrastructure (so any one else working on deprecations will be blocked anyways).

@t-sauer
Copy link
Contributor

t-sauer commented Nov 29, 2017

I'd like to work on 'phantomjs support / hacks' if that is still up for grabs

@sivakumar-kailasam
Copy link
Member

@t-sauer I'm ready to raise a PR for that 😅

@t-sauer
Copy link
Contributor

t-sauer commented Nov 29, 2017

Well then I'll pick "Remove console polyfills / shims in packages/ember-console/lib/index.js" 🤞

@maxscott
Copy link
Contributor

Ill take a stab at Remove custom Map from packages/ember-metal/lib/map.js

@locks
Copy link
Contributor

locks commented Nov 29, 2017

Taking Ember.String.fmt: #15882.

@locks
Copy link
Contributor

locks commented Nov 29, 2017

Taking this.resource on RouterDSL: #15883.

@locks
Copy link
Contributor

locks commented Nov 29, 2017

Taking link-to's currentWhen: #15884.

@locks
Copy link
Contributor

locks commented Nov 29, 2017

Taking "Arity check for initializers": #15886.

@rwjblue
Copy link
Member Author

rwjblue commented Nov 29, 2017

@locks one thing to keep in mind, is that we can't remove the functionality completely just yet. We have to either add it to https://github.com/emberjs/ember-2-legacy or wrap it in a conditional flag.

This is due to our stated goal from the 3.0 blog post:

To further expand the migration window for 2.x applications to adopt 3.x, we will be releasing an addon that provides support for Ember.js 2.x APIs into the 3.x series. We’re committing to support that addon until Ember 3.4 (the first LTS candidate of the Ember 3.x cycle). If you want to contribute to this effort, you can find this package under the name ember-2-legacy.

@locks
Copy link
Contributor

locks commented Nov 29, 2017

@rwjblue roger that 👍 I will review per-feature what the best approach might be. I'm partial to moving the implementation to the legacy addon if possible, if nothing else it seems neater.

@rwjblue
Copy link
Member Author

rwjblue commented Nov 29, 2017

Absolutely agreed! We just need to ensure we have a path forward. Things like fooBinding support will almost certainly have to be wrapped in conditionals here. But things like Ember.String.fmt and link-to currentWhen can totally be done in the addon itself directly.

@cibernox
Copy link
Contributor

Enumerable#contains
#15889

@bekzod
Copy link
Contributor

bekzod commented Nov 30, 2017

Taking Ember.Freezable #15891

@bekzod
Copy link
Contributor

bekzod commented Nov 30, 2017

Taking Ember.REQUIRED #15892

@bekzod
Copy link
Contributor

bekzod commented Nov 30, 2017

Taking Ember.observer(callback, 'dependent-key1', 'dependent-key2') #15893

@bekzod
Copy link
Contributor

bekzod commented Nov 30, 2017

Taking immediateObserver #15894

@thoov
Copy link
Member

thoov commented Dec 1, 2017

@rwjblue Lock me up on:

Ember.Component#defaultLayout
_actions
render
Legacy controller proxying behaviors
didInit

@rwjblue
Copy link
Member Author

rwjblue commented Dec 1, 2017

@thoov - Done (but defaultLayout was already taken by @romulomachado in #15896)

@rwjblue
Copy link
Member Author

rwjblue commented Dec 1, 2017

I believe I have everything triaged, please ping me (probably in #dev-ember in slack) if I've missed something...

@bekzod
Copy link
Contributor

bekzod commented Dec 1, 2017

Taking Transforming {{input on="enter" action="foo"}} to {{input enter="foo"}} #15910

@cibernox
Copy link
Contributor

cibernox commented Dec 1, 2017

Is there anything not claimed? It seems that fooBinding is free

@cibernox
Copy link
Contributor

cibernox commented Dec 1, 2017

I take {Application,Engine,ApplicationInstance}.registry

@gowthamrm
Copy link
Contributor

gowthamrm commented Dec 1, 2017

Taking Providing resolver as a function to the registry

Fixed in #15911

@lorcan
Copy link
Contributor

lorcan commented Dec 2, 2017

I took a stab at Orphaned outlets here, here, and here: #15916

lorcan added a commit to lorcan/ember.js that referenced this issue Dec 2, 2017
lorcan added a commit to lorcan/ember.js that referenced this issue Dec 2, 2017
lorcan added a commit to lorcan/ember.js that referenced this issue Dec 2, 2017
@alexander-alvarez
Copy link
Contributor

@rwjblue we need to update the testing blueprints... not sure if this is explicitly 3.0 related

@rwjblue
Copy link
Member Author

rwjblue commented Dec 3, 2017

@alexander-alvarez - You are absolutely right! I will try to get another quest issue together for the blueprints in the next day or so...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests