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

(feat): show glossary terms in hierarchy form #15823

Merged

Conversation

harsh-vador
Copy link
Contributor

@harsh-vador harsh-vador commented Apr 5, 2024

Describe your changes:

Fixes: #13917, #10724

Screen.Recording.2024-04-20.at.3.21.25.PM.mov

I worked on showing the glossary terms in hierarchical way in entity right panel.

Type of change:

  • Improvement

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@github-actions github-actions bot added e2e:Governance UI UI specific issues and removed e2e:Governance labels Apr 5, 2024
Copy link
Contributor

github-actions bot commented Apr 5, 2024

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

@chirag-madlani chirag-madlani force-pushed the glossary-terms-hierarchy branch from bcd76ff to 1d33939 Compare April 12, 2024 10:23
Copy link
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

Copy link
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

Copy link
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

Copy link
Contributor

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

@chirag-madlani chirag-madlani added the safe to test Add this label to run secure Github workflows on PRs label Apr 18, 2024
Copy link
Contributor

github-actions bot commented Apr 21, 2024

Jest test Coverage

UI tests summary

Lines Statements Branches Functions
Coverage: 64%
64.72% (33964/52476) 41.84% (13310/31815) 43.35% (4175/9630)

Copy link

cypress bot commented Apr 21, 2024

1 failed test on run #33991 ↗︎

1 520 0 0 Flakiness 0

Details:

fix count issue for tags page
Project: openmetadata Commit: 2017bdaa48
Status: Failed Duration: 50:41 💡
Started: Apr 26, 2024 6:23 AM Ended: Apr 26, 2024 7:13 AM
Failed  cypress/e2e/Service/ServiceIngestion.spec.ts • 1 failed test • cypress-ci-mysql-pr-8843847748-1

View Output Video

Test Artifacts
Airflow Ingestion > Create & Ingest Airflow service Screenshots Video

Review all test suite changes for PR #15823 ↗︎

Copy link
Contributor

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

1 similar comment
Copy link
Contributor

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR.
You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

Copy link
Contributor

@ShaileshParmar11 ShaileshParmar11 left a comment

Choose a reason for hiding this comment

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

left few comments

Copy link

@chirag-madlani chirag-madlani merged commit 5125ebc into open-metadata:main Apr 26, 2024
10 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2e:Governance e2e:Integration e2e:Settings safe to test Add this label to run secure Github workflows on PRs UI UI specific issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tag suggested window covers it's action button
4 participants