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

Fixed scalar card header description bug #1390

Merged
merged 1 commit into from
Sep 5, 2018

Conversation

stephanwlee
Copy link
Contributor

As part of refactor, the categorization now returns series instead of tag and runs. This broke _tagMetadata not to be invoked by Polymer.

Also, the change trims scalar card title if it matches prefix.

// of the scalar-card if name != prefix.
if (category.metadata.type ==
tf_categorization_utils.CategoryType.PREFIX_GROUP &&
category.name != displayName &&
Copy link
Contributor

Choose a reason for hiding this comment

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

This check is redundant with the next line

runToTagInfo,
defaultDisplayName);

// If category name is a prefix group, strip the prefix from the name
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this addressing #1389? If so, awesome, but ideally better to have a new feature in a separate PR rather than bundled in with a bugfix. Makes it easier for writing release notes, etc. if new features come in their own PRs.

@stephanwlee
Copy link
Contributor Author

Move the unnecessary change into a separate PR. Sorry about that

As part of refactor, the categorization now returns series instead of
tag and runs. This broke `_tagMetadata` not to be invoked by Polymer.
@stephanwlee stephanwlee merged commit 6ec7739 into tensorflow:master Sep 5, 2018
@stephanwlee stephanwlee deleted the name branch September 5, 2018 02:03
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