You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In case of combined CropPage + CropOnMarkers usecase, sometimes the page boundary is not visible but the markers can still be detected. Currently in this case CropPage raises an error for the image since it thinks the image is not fit for processing further.
Describe the solution you'd like
We should allow a flag shouldFailIfPageNotFound which would be set to true by default. On setting it as false, the CropPage processor should return the input image without cropping.
Describe alternatives you've considered
Another alternative is to create a new processor that does this instead of a flag, but seems unnecessary as of now.
Is your feature request related to a problem? Please describe.
In case of combined CropPage + CropOnMarkers usecase, sometimes the page boundary is not visible but the markers can still be detected. Currently in this case CropPage raises an error for the image since it thinks the image is not fit for processing further.
Describe the solution you'd like
We should allow a flag
shouldFailIfPageNotFound
which would be set to true by default. On setting it as false, the CropPage processor should return the input image without cropping.Describe alternatives you've considered
Another alternative is to create a new processor that does this instead of a flag, but seems unnecessary as of now.
Additional context
The text was updated successfully, but these errors were encountered: