fix(typescript): rename services to fix typescript (#3165)
* fix: Rename services to lower camel case, hp, measure * fix: Rename DisplaySetService instances to displaySetService * fix: Rename CornerstoneViewportService to lower camel case * fix: Added lower case segmentationService rename * rename other services (#3166) * rename uiDialogService * rename toolGroupService * rename uiNotificationService * rename viewportGridService * rename syncGroupService * rename CornerstoneCacheService * Fix a syntax error in hotkeys * Fix a couple of rename issues that were missed --------- Co-authored-by: Alireza <ar.sedghi@gmail.com>
This commit is contained in:
1 parent
a97fb2fc9a
commit
8af0362d12
97 files changed
+934
-908
No files matched your search
@@ -4,8 +4,8 @@ import { ArrowAnnotateTool } from '@cornerstonejs/tools';
|
||||
* The reason we are extending ArrowAnnotateTool is to create a new tool for SR
|
||||
* viewport which basically has a different name. This is done since Cornerstone
|
||||
* has shifted from creating tool instances for each annotation, and we have ArrowAnnotate
|
||||
* mappers at the MeasurementService, so if we didn't do this, we would be mapping
|
||||
* the SR annotation to the MeasurementService (since there is a ArrowAnnotateTool mapper),
|
||||
* mappers at the measurementService, so if we didn't do this, we would be mapping
|
||||
* the SR annotation to the measurementService (since there is a ArrowAnnotateTool mapper),
|
||||
* but with extending and renaming it, there is not mapper for SRArrowAnnotateTool; hence
|
||||
* no mapping; hence no new measurement, just temporary ones for the SR viewport.
|
||||
*/
|
||||
|
||||
@@ -4,8 +4,8 @@ import { BidirectionalTool } from '@cornerstonejs/tools';
|
||||
* The reason we are extending BidirectionalTool is to create a new tool for SR
|
||||
* viewport which basically has a different name. This is done since Cornerstone
|
||||
* has shifted from creating tool instances for each annotation, and we have Bidirectional
|
||||
* mappers at the MeasurementService, so if we didn't do this, we would be mapping
|
||||
* the SR annotation to the MeasurementService (since there is a BidirectionalTool mapper),
|
||||
* mappers at the measurementService, so if we didn't do this, we would be mapping
|
||||
* the SR annotation to the measurementService (since there is a BidirectionalTool mapper),
|
||||
* but with extending and renaming it, there is not mapper for SRBidirectionalTool; hence
|
||||
* no mapping; hence no new measurement, just temporary ones for the SR viewport.
|
||||
*/
|
||||
|
||||
@@ -4,8 +4,8 @@ import { EllipticalROITool } from '@cornerstonejs/tools';
|
||||
* The reason we are extending EllipticalROITool is to create a new tool for SR
|
||||
* viewport which basically has a different name. This is done since Cornerstone
|
||||
* has shifted from creating tool instances for each annotation, and we have EllipticalROI
|
||||
* mappers at the MeasurementService, so if we didn't do this, we would be mapping
|
||||
* the SR annotation to the MeasurementService (since there is a EllipticalROITool mapper),
|
||||
* mappers at the measurementService, so if we didn't do this, we would be mapping
|
||||
* the SR annotation to the measurementService (since there is a EllipticalROITool mapper),
|
||||
* but with extending and renaming it, there is not mapper for SREllipticalROITool; hence
|
||||
* no mapping; hence no new measurement, just temporary ones for the SR viewport.
|
||||
*/
|
||||
|
||||
@@ -4,8 +4,8 @@ import { LengthTool } from '@cornerstonejs/tools';
|
||||
* The reason we are extending LengthTool is to create a new tool for SR
|
||||
* viewport which basically has a different name. This is done since Cornerstone
|
||||
* has shifted from creating tool instances for each annotation, and we have Length
|
||||
* mappers at the MeasurementService, so if we didn't do this, we would be mapping
|
||||
* the SR annotation to the MeasurementService (since there is a LengthTool mapper),
|
||||
* mappers at the measurementService, so if we didn't do this, we would be mapping
|
||||
* the SR annotation to the measurementService (since there is a LengthTool mapper),
|
||||
* but with extending and renaming it, there is not mapper for SRLengthTool; hence
|
||||
* no mapping; hence no new measurement, just temporary ones for the SR viewport.
|
||||
*/
|
||||
|
||||
Reference in new issue
Block a user