-
-
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
MANDATORY_SETTER_FUNCTION assertion causes errors on Component teardown with HTMLBars #10935
Comments
This is specifically happening somewhere within the ember-nf-graph nf-graph-content component ... and it only started after I upgraded to Ember |
|
I did a quick scan through the repo, and do not see an instance of you observing |
The only thing I can think of is that I'm accessing that DOM element via something like D3 in another component. FWIW: I looked through version history and found that it used to use set in that area: 6af9b03#diff-d8303a7a1692ae012d56a3c6dad4ed2dL139 |
... but access it via D3 wouldn't cause that right? It seems like something set up the |
if you use another views |
So, I suppose it depends how you use the element... |
That's probably what's happening. |
FWIW: Because Ember is so consistent, this seems like a "wat" in Ember. Everything else in Ember is delightfully uniform or at least gives you clean errors/assertions if you abuse a thing. As an author, I just assumed that Ember, being Ember, would allow me to observe, depend on, or get damn near anything |
I'm currently consistantly running into an issue where Ember setting
view.element = null;
apparently on this line in HTMLBarsCauses an assertion error that is unhandled and breaking our app. Here's a screenshot:
The text was updated successfully, but these errors were encountered: