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

Add safeSet for Ember tracking context #395

Merged
merged 8 commits into from
Jan 11, 2020
Merged

Add safeSet for Ember tracking context #395

merged 8 commits into from
Jan 11, 2020

Conversation

snewcomer
Copy link
Collaborator

close #394

@josemarluedke 👋 Thank you for the issue! I believe this is because we need to use Ember.set. This PR makes it work.

One question is - what was the reason to track the model on the Component instance in your example? At first I assumed this wasn't necessary. Let me know your thoughts!

@snewcomer snewcomer added the bug label Jan 10, 2020
@snewcomer snewcomer self-assigned this Jan 10, 2020
@josemarluedke
Copy link
Contributor

@snewcomer Thanks for working on this. I don't think the tracked is going to be required as I had in the example. I used it as a way to see if would help with anything.

@snewcomer snewcomer merged commit 02b6ca0 into master Jan 11, 2020
@snewcomer snewcomer deleted the sn/dummy-form branch January 11, 2020 01:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[3.0.0-beta.4] mutating the model in Glimmer Components
2 participants