Refactor run method inparent #780
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
…ultiple components for consistency and clarity. - Updated method signatures and calls in various components including Festo, Keyence, Kuka, Mitsubishi, Rexroth, Pneumatics, and Siemens. - Ensured all instances of 'parent' were replaced with 'inParent' in method definitions and calls. - Adjusted related documentation to reflect the new parameter naming.
…e components - Updated method signatures and calls in AxoInsight, AxoVisionPro, and various Desoutter, Drives, Dukane, Keyence, Rexroth, and Mitsubishi components to replace 'parent' with 'inParent'. - Adjusted related documentation to reflect the new parameter naming. - Ensured consistency in method calls and error handling checks for null values.
…aming' for clarity
…efactor parameter naming from 'Parent' to 'inParent' in AxoBlinker method.
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.
This pull request standardizes the naming of the parent object parameter across multiple component libraries by renaming it from
parenttoinParent. The change is consistently applied in method signatures, calls, and internal logic for ABB Robotics, Balluff Identification, and Cognex Vision components. This improves code clarity and consistency, making it easier to understand and maintain.Parameter Renaming and Consistency
parentparameter toinParentin allRunmethod signatures, calls, and related logic for ABB Robotics components (includingAxoIrc5_v_1_x_xandAxoOmnicore_v_1_x_x) and updated all usages in documentation and sandbox files. [1] [2] [3] [4] [5] [6] [7] [8] [9]parentparameter toinParentin Balluff Identification component methods and updated all usages in documentation and sandbox files. [1] [2] [3] [4] [5]parentparameter toinParentin Cognex Vision component methods and updated all usages in documentation, sandbox, and control files. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]Internal Logic Updates
inParentinstead ofparent, ensuring consistent null checks and error reporting throughout ABB Robotics, Balluff Identification, and Cognex Vision components. [1] [2] [3] [4] [5] [6] [7] [8] [9]Documentation and Sandbox Updates
inParentparameter name in all relevant method calls and examples, ensuring that usage examples reflect the new standard. [1] [2] [3]These changes collectively improve code readability and maintainability by enforcing a consistent naming convention for parent object parameters across all supported device components.