feat: update to ohif 3.11 #1855
Open
Conversation
This file contains hidden or 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
Signed-off-by: yanq <[email protected]>
for more information, see https://pre-commit.ci Signed-off-by: yanq <[email protected]>
Signed-off-by: Qingyu Yan <[email protected]> Signed-off-by: yanq <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
feat: Upgrade OHIF to v3.11 with new UI components and services
This pull request upgrades our application to support the latest features and architectural improvements in OHIF v3.11. The update focuses on modernizing the UI and integrating new, centralized services for a more modular and consistent user experience.
Key Changes & Features
@ohif/ui-nextpackage.ToolbarService: The legacy toolbar system has been replaced with the newToolbarServiceAPI.modalityLoadBadgetrackingStatusnavigationComponentValidation Status & Scope
Limited Testing Scope: Due to the scope of this PR, comprehensive testing across all models was not performed.
Functionality Verified: The segmentation functionality has been verified and is confirmed to be working as expected.
Please review it
@sedghi @SachidanandAlle