feat(ui): what's new details update for 1.4.0 #16146
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
safe to test
pmbrull
reviewed
May 9, 2024
openmetadata-ui/src/main/resources/ui/src/components/Modals/WhatsNewModal/whatsNewData.ts
Outdated
Show resolved
Hide resolved
openmetadata-ui/src/main/resources/ui/src/components/Modals/WhatsNewModal/whatsNewData.ts
Outdated
Show resolved
Hide resolved
Jest test CoverageUI tests summary
|
Ashish8689
requested review from
harshach,
karanh37,
chirag-madlani and
Sachin-chaurasiya
as code owners
karanh37
previously approved these changes
May 16, 2024
Sachin-chaurasiya
previously approved these changes
May 16, 2024
| - bootstrap/bootstrap_storage.sh has been deprecated in favor of bootstrap/openmetadata-ops.sh | ||
|
|
||
| UI: | ||
|
|
There was a problem hiding this comment.
No need for extra space after sub-header for UI and API sections
|
|
||
| - Activity has been improved. New update specific cards display critical information such as data quality test case updates, description, tag update or removal. | ||
| - For Lineage, the Expand All button has been removed. A new Layers button is introduced at the bottom left corner. With the Layers button, you can add Column Level Lineage or Data Observability details to your Lineage view. | ||
| - View Definition is now renamed to Schema Definition. |
pmbrull
previously approved these changes
May 16, 2024
| - For Lineage, the Expand All button has been removed. A new Layers button is introduced at the bottom left corner. With the Layers button, you can add Column Level Lineage or Data Observability details to your Lineage view. | ||
| - View Definition is now renamed to Schema Definition. | ||
| - Adding Glossary Term view is improved. Now we show glossary terms hierarchically enabling a better understanding of how the terms are setup while adding it to a table or dashboard. | ||
| - For Classification, users can set classification to be mutually exclusive only at the creation time. Once created, you cannot change it back to mutually non-exclusive or vice-versa. This is to prevent conflicts of adding multiple tags that belong to same classification and later turning the mutually exclusive flag back to true. |
There was a problem hiding this comment.
For Classification, users can set classification to be mutually exclusive only **at the time of creation**. Once created, you cannot change it back to mutually non-exclusive or vice-versa. This is to prevent conflicts of adding multiple tags that belong to same classification and later turning the mutually exclusive flag back to true.
ShilpaVernekar
previously approved these changes
May 16, 2024
ShaileshParmar11
dismissed stale reviews from ShilpaVernekar, pmbrull, Sachin-chaurasiya, and karanh37
via
45e4dff
ShilpaVernekar
approved these changes
May 16, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes:
Fixes
Fixes: Update what's new content for 1.4.0
Screen.Recording.2024-05-16.at.3.34.35.PM.mov
Type of change:
Checklist:
Fixes <issue-number>: <short explanation>