QA: Replacement test case for 3rd party class containing ZendForm in its full path #94
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.
Signed-off-by: Patrick Braun patrick.braun@krumedia.com
Description
Corresponding test to issue #93
Adds unit test that is currently failing because the replacement rules replace the word ZendForm in 3rd party paths, which it should not do.
How to reproduce
Try to use a custom class that contains "ZendForm" somewhere in its class path, it'll get renamed to LaminasForm.
Expected:
CustomZendFormBinder => CustomZendFormBinder
Actual:
CustomZendFormBinder => CustomLaminasFormBinder