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

[BUGFIX beta] Avoid isEmpty for known object types. #5341

Merged
merged 1 commit into from
Mar 5, 2018

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Jan 28, 2018

Ember.isEmpty does a lot of things, there is no reason to use it when you are operating on known data types.

Use the platform...

@bmac
Copy link
Member

bmac commented Feb 28, 2018

@rwjblue do you mind rebasing this pr?

`Ember.isEmpty` does **a lot of things**, there is no reason to use it
when you are operating on known data types.

**_Use the platform..._**
@bmac bmac merged commit 77a9fef into emberjs:master Mar 5, 2018
@bmac
Copy link
Member

bmac commented Mar 5, 2018

Thanks @rwjblue.

@rwjblue rwjblue deleted the avoid-is-empty branch March 5, 2018 18:37
bmac pushed a commit that referenced this pull request Mar 15, 2018
`Ember.isEmpty` does **a lot of things**, there is no reason to use it
when you are operating on known data types.

**_Use the platform..._**

(cherry picked from commit 77a9fef)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants