Fix for issue #7355#7357
Merged
Merged
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
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.
Task: hardening the Apache Hop Testing Plugin, issue #7355
This report outlines the completed fixes and enhancements implemented in the Apache Hop codebase to resolve the problems described in the issue.
1. CSV Loader Safety (Out of Bounds Errors)
ArrayIndexOutOfBoundsExceptionerrors.ing
setRowMeta.getValueMeta(...)andcsvRecord.get(...). Any missing or out-of-bound columns default gracefully tonullinstead of throwing exceptions.getMappedDataSetFieldsRowMetato construct a dummyValueMetaStri ngif a mapped field does not exist in the dataset metadata, preventing downstream NullPointerExceptions and metadata mismatches.2. Open Selected Unit Test from Workflow Actions
D ataSetConst.VAR_UNIT_TEST_NAMEenvironment variable (using reflection to accessHopGuivariables safely to maintain headless environment compatibility).DataSetConst.VA R_UNIT_TEST_NAMEduring thePipelineAfterOpenextension point. If specified, the requested unit test is activated, and the variable is subsequently cleared.3. Dataset Location Dialog Validation
validate()check that:CheckResultDialogor a popup message box.4. Context Menu Override on Golden Dataset Arrow Click
PipelineGr aphMouseUpextension point.MouseUpevents on the canvas: if the clicked AreaOwner belongs toAREA_DRAWN_INPUT_DATA_SET,AREA_DRAWN_GOLDEN_DATA_SET, orAREA_DRAWN_GOLDEN_DATA_RESULT, it setspipelineGraphExtension.setP reventingDefault(true), stopping the pipeline context dialog from appearing.