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] Fixes args tracking in Glimmer component #180

Merged
merged 2 commits into from
Mar 18, 2019

Conversation

pzuraq
Copy link
Member

@pzuraq pzuraq commented Mar 16, 2019

@tracked is not yet avalibale for general usage in Ember apps,
so we were relying on using the interop with get and
set to track args. However, we never actually used get,
so it wasn't picking it up. This ensures that all gets/sets of
the field go through the proper codepaths, and will be autotracked.

Chris Garrett added 2 commits March 15, 2019 17:28
`@tracked` is not yet avalibale for general usage in Ember apps,
so we were relying on using the interop with `get` and
`set` to track args. However, we never actually used `get`,
so it wasn't picking it up. This ensures that all gets/sets of
the field go through the proper codepaths, and will be autotracked.
@rwjblue
Copy link
Member

rwjblue commented Mar 16, 2019

This seems fine for now, but I would like to update to something akin to what was done in:

a7d5fb6

Even though that was for glimmer.js's version, the code is roughly the same in Ember (going back a ways now).

Copy link
Member

@rwjblue rwjblue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good enough for me! But I would like to migrate this to direct tag dirtying sometime after EmberConf...

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.

2 participants