Skip to content

feature: query lineage visualizer advanced styling & interactive component handling #4

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

Merged
merged 17 commits into from
Jul 26, 2022

Conversation

ytlee93
Copy link
Collaborator

@ytlee93 ytlee93 commented Jul 20, 2022

Issue #, if available:

Description of changes:

  • advanced styling including color by lineage entity, star shape startarn nodes and legend section
  • callback events on selecting nodes which nodes will be highlighted on click

image

Testing done:
tox -e black-format & tox -e flake8,pylint,twine,black-check,docstyle --parallel all
tox -e py39 tests/unit/sagemaker/lineage
tox -e py39 tests/integ/sagemaker/lineage

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

  • I have read the CONTRIBUTING doc
  • I certify that the changes I am introducing will be backward compatible, and I have discussed concerns about this, if any, with the Python SDK team
  • I used the commit message format described in CONTRIBUTING
  • I have passed the region in to all S3 and STS clients that I've initialized as part of this change.
  • I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have added unit and/or integration tests as appropriate to ensure backward compatibility of the changes
  • I have checked that my tests are not configured for a specific region or account (if appropriate)
  • I have used unique_name_from_base to create resource names in integ tests (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jkasiraj
Copy link
Owner

The graph looks nice!

),
# legend section
self.html.Div(
[self._create_legend_component(k, v) for k, v in self.entity_color.items()]
Copy link
Owner

Choose a reason for hiding this comment

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

Won't this result in the string TrialComponent being shown instead of Trial Component? Could either string split on capitalization or just include the title in the config as well as the selector id

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

resolved

Copy link
Collaborator

@Snoyark Snoyark left a comment

Choose a reason for hiding this comment

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

Looks good!

@ytlee93 ytlee93 merged commit e6078a9 into jkasiraj:master Jul 26, 2022
ytlee93 referenced this pull request in ytlee93/sagemaker-python-sdk Jul 27, 2022
Merge pull request #4 from ytlee93/master
ytlee93 added a commit that referenced this pull request Aug 5, 2022
Merge pull request #6 from ytlee93/master
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.

3 participants