-
Notifications
You must be signed in to change notification settings - Fork 882
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
[navigation-next] feat: introduce new interface for group #7060
[navigation-next] feat: introduce new interface for group #7060
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7060 +/- ##
==========================================
+ Coverage 67.45% 67.48% +0.02%
==========================================
Files 3448 3451 +3
Lines 67964 68060 +96
Branches 11057 11068 +11
==========================================
+ Hits 45845 45928 +83
- Misses 19446 19454 +8
- Partials 2673 2678 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…project#7060) Signed-off-by: SuZhou-Joe <[email protected]>
Signed-off-by: SuZhou-Joe <[email protected]>
Signed-off-by: SuZhou-Joe <[email protected]>
Signed-off-by: SuZhou-Joe <[email protected]>
src/core/types/nav_group.ts
Outdated
* Groups with type of NavGroupType.SYSTEM will: | ||
* 1. Always display before USE_CASE_GROUP. | ||
* 2. Not be pickable within the workspace creation page. | ||
* | ||
* @default undefined indicates it is of type useCase |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this comment be adjusted a bit? Maybe the comment should be not in core, but at where the type
is used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, move the comment to the enum NavGroupType, and the place which will use this type is in another PR and still waiting for finalized design.
Signed-off-by: SuZhou-Joe <[email protected]>
Signed-off-by: SuZhou-Joe <[email protected]>
…project#7060) Signed-off-by: SuZhou-Joe <[email protected]>
The backport to
To backport manually, run these commands in your terminal: # Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-7060-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5212f09b780459c8212697a419d5651b83361d6d
# Push it to GitHub
git push --set-upstream origin backport/backport-7060-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x Then, create a pull request where the |
…-project#7060) * feat: introduce new interface for use case Signed-off-by: SuZhou-Joe <[email protected]> * Changeset file for PR opensearch-project#7060 created/updated * feat: introduce new interface for use case Signed-off-by: SuZhou-Joe <[email protected]> * feat: introduce new interface for use case Signed-off-by: SuZhou-Joe <[email protected]> * feat: introduce new interface for use case Signed-off-by: SuZhou-Joe <[email protected]> * fix: update test snapshot Signed-off-by: SuZhou-Joe <[email protected]> * fix: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * Changeset file for PR opensearch-project#7060 created/updated * fix: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * fix: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * fix: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: update comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: add default nav group Signed-off-by: SuZhou-Joe <[email protected]> * fix: type error Signed-off-by: SuZhou-Joe <[email protected]> * fix: type error Signed-off-by: SuZhou-Joe <[email protected]> * feat: expose DEFAULT_NAV_GROUPS in src/core/public Signed-off-by: SuZhou-Joe <[email protected]> * feat: export NavGroupItemInMap type Signed-off-by: SuZhou-Joe <[email protected]> * feat: update README Signed-off-by: SuZhou-Joe <[email protected]> * feat: update README Signed-off-by: SuZhou-Joe <[email protected]> * feat: update interface Signed-off-by: SuZhou-Joe <[email protected]> * refactor: move navGroup related interface into a service Signed-off-by: SuZhou-Joe <[email protected]> * feat: remove useless code Signed-off-by: SuZhou-Joe <[email protected]> * [Navigation-Next] Add nav group enabled in chrome service(7072) Signed-off-by: SuZhou-Joe <[email protected]> * Remove useless code Signed-off-by: SuZhou-Joe <[email protected]> * use homepage flag Signed-off-by: SuZhou-Joe <[email protected]> * feat: update README Signed-off-by: SuZhou-Joe <[email protected]> * feat: expose sorted navLinks Signed-off-by: SuZhou-Joe <[email protected]> * fix: unit test Signed-off-by: SuZhou-Joe <[email protected]> * fix: bootstrap error Signed-off-by: SuZhou-Joe <[email protected]> * fix: snapshot error Signed-off-by: SuZhou-Joe <[email protected]> * feat: update according to comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: support parent link Signed-off-by: SuZhou-Joe <[email protected]> * feat: update according to comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: update according to comment Signed-off-by: SuZhou-Joe <[email protected]> --------- Signed-off-by: SuZhou-Joe <[email protected]> Co-authored-by: opensearch-changeset-bot[bot] <154024398+opensearch-changeset-bot[bot]@users.noreply.github.com> Co-authored-by: ZilongX <[email protected]> (cherry picked from commit 5212f09)
) * feat: introduce new interface for use case Signed-off-by: SuZhou-Joe <[email protected]> * Changeset file for PR #7060 created/updated * feat: introduce new interface for use case Signed-off-by: SuZhou-Joe <[email protected]> * feat: introduce new interface for use case Signed-off-by: SuZhou-Joe <[email protected]> * feat: introduce new interface for use case Signed-off-by: SuZhou-Joe <[email protected]> * fix: update test snapshot Signed-off-by: SuZhou-Joe <[email protected]> * fix: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * Changeset file for PR #7060 created/updated * fix: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * fix: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * fix: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: update based on comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: update comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: add default nav group Signed-off-by: SuZhou-Joe <[email protected]> * fix: type error Signed-off-by: SuZhou-Joe <[email protected]> * fix: type error Signed-off-by: SuZhou-Joe <[email protected]> * feat: expose DEFAULT_NAV_GROUPS in src/core/public Signed-off-by: SuZhou-Joe <[email protected]> * feat: export NavGroupItemInMap type Signed-off-by: SuZhou-Joe <[email protected]> * feat: update README Signed-off-by: SuZhou-Joe <[email protected]> * feat: update README Signed-off-by: SuZhou-Joe <[email protected]> * feat: update interface Signed-off-by: SuZhou-Joe <[email protected]> * refactor: move navGroup related interface into a service Signed-off-by: SuZhou-Joe <[email protected]> * feat: remove useless code Signed-off-by: SuZhou-Joe <[email protected]> * [Navigation-Next] Add nav group enabled in chrome service(7072) Signed-off-by: SuZhou-Joe <[email protected]> * Remove useless code Signed-off-by: SuZhou-Joe <[email protected]> * use homepage flag Signed-off-by: SuZhou-Joe <[email protected]> * feat: update README Signed-off-by: SuZhou-Joe <[email protected]> * feat: expose sorted navLinks Signed-off-by: SuZhou-Joe <[email protected]> * fix: unit test Signed-off-by: SuZhou-Joe <[email protected]> * fix: bootstrap error Signed-off-by: SuZhou-Joe <[email protected]> * fix: snapshot error Signed-off-by: SuZhou-Joe <[email protected]> * feat: update according to comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: support parent link Signed-off-by: SuZhou-Joe <[email protected]> * feat: update according to comment Signed-off-by: SuZhou-Joe <[email protected]> * feat: update according to comment Signed-off-by: SuZhou-Joe <[email protected]> --------- Signed-off-by: SuZhou-Joe <[email protected]> Co-authored-by: opensearch-changeset-bot[bot] <154024398+opensearch-changeset-bot[bot]@users.noreply.github.com> Co-authored-by: ZilongX <[email protected]> (cherry picked from commit 5212f09)
#7136 Remove failed backport as it has been manually backported. |
Description
This PR mainly introduces new interface to register and get useCases from chrome service, and it is a fundamental change for the new navigation.
Issues Resolved
closes #7061
Screenshot
No UI changes.
Testing the changes
As there is no place using the new interfaces introduced in this PR. You can refer to the test cases here:
src/core/public/chrome/chrome_service.test.ts
Changelog
Check List
yarn test:jest
yarn test:jest_integration