Skip to content

Conversation

@stephanwlee
Copy link
Contributor

tf-tag-filterer, correctly, defined its property tag-filter as
readOnly and this broke the data connection between paper-input.
Between the paper-input and the filterer, there should be a
two-way binding of its value whereas all the consumers of the
tf-tag-filterer should only read from the component.

Now, using the private property, _tagFilter, we establish the two-way
binding while the public property is only used to publish the change.

Note: bug was introduced over #1483, #1475, and #1493.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'd call this _computeTagFilter() for consistency with the other computed property methods, even though this one doesn't really do meaningful computation. It's also pretty weird for a method named "setXX" to actually have no direct side effects (and which looks like a vanilla getter).

tf-tag-filterer, correctly, defined its property `tag-filter` as
readOnly and this broke the data connection between `paper-input`.
Between the paper-input and the filterer, there should be a
two-way binding of its value whereas all the consumers of the
tf-tag-filterer should only read from the component.

Now, using the private property, `_tagFilter`, we establish the two-way
binding while the public property is only used to publish the change.

Note: bug was introduced over tensorflow#1483, tensorflow#1475, and tensorflow#1493.
@stephanwlee stephanwlee merged commit a24efd5 into tensorflow:master Oct 10, 2018
@stephanwlee stephanwlee deleted the stupid branch October 10, 2018 23:35
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.

2 participants