-
Notifications
You must be signed in to change notification settings - Fork 576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow support for using an image after instantiation #251
Conversation
Not quite sure why the Bitrise check fails, any idea what the underlying error might be? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution. I've got a few points of feedback regarding unneeded self
usage.
Bitrise is running too and was shown as "failed" as it was never started. It requires manually acceptance for external PRs.
Thanks!
WeScan.framework: Coverage: 41.03
Generated by 🚫 Danger Swift against 41a7363 |
Updated PR with code review feedback! :) |
Congratulations! 🎉 This was released as part of Release 1.6.0 🚀 Generated by GitBuddy |
This change moves quad detection code into the method
detect(image:)
so it can be accessed post-instantiation. This is utilized byuseImage(image:)
, which will push anEditScanViewController
even after the main VC is presented. For an example of how I've been using this in production, see this video.I also made
ScannerViewController
public so client code can inspect the controller hierarchy for this specific controller.