Image search easyocr one #375
Merged
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.
PR Type
------Implemented "easyocr" tool which can work as an alternative to image text.
This was implemented to detect elements on low resolution pc as oftentime pytesseract fails to detect element on low res pc , or some time in some page ..this can work as an alternative to detect those elements..
parameters and their explanation:
-easyocr_paragraph = "If you set it true , it will return value in paragraphs instead of individual text"
-t_screenshot = "In the produced output , if the desired text has random characters in them ,you can use this functionality to detect it accurately."
Since easy_ocr works bit slower when uses CPU , I have added this improvement to fasten automation process.
if user is working with multiple elements from the same page , previously the node used easy_ocr tool each single time to identify elements which slowed down automation quiet a bit.
So to tackle the issue , I have implemented a row which will store a single run value inside a variable meaning if the user is planning to work with multiple elements from same page , user will just have to run the easy_ocr tool with action for once and then it will store the value inside a variable.
Then on the next action user will just have to use that variable to work with other element from same page . And user won't have to wait for longer time like he/she used to.
to store value , use "store_data" | element parameter | "provide variable name"
And to use the stored value , you use "previous_value" | element parameter | %| provide variable name|%
PR Checklist
Overview
Test Cases