-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PERF] Model.prototype.didDefineProperty only in dev #4924
Conversation
@@ -1924,4 +1884,47 @@ if (isEnabled('ds-rollback-attribute')) { | |||
}); | |||
} | |||
|
|||
runInDebug(() => { | |||
Model.reopen({ |
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.
I believe this should be reopenClass as this was a static method?
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.
actually scratch that I think I read the diff wrong on the original location.
|
@stefanpenner this is fixed by another of my PR's, the issue is that the env is "test" at runtime but "production" at build time, so our code stripping needs to take account a little differently. |
@stefanpenner actually, looks like you merged it: #4920 Try a rebase. |
`meta.parentType` (which is produced by) `didDefineProperty` is only required for development assertions. As development assertions are stripped in prod, this `didDefineProperty` can also be stripped
60d5df8
to
23503f8
Compare
Also tidying up the other side of this in ember emberjs/ember.js#15141 (no cross dependencies exist) |
meta.parentType
(which is produced by)didDefineProperty
is only required for development assertions. As development assertions are stripped in prod, thisdidDefineProperty
can also be stripped