-
Notifications
You must be signed in to change notification settings - Fork 9.7k
[firebase_ml_vision] adds facial contours #1599
Conversation
modified .gitignore to ommit some vscode related directories. added contours to both android and iOS. I'm not sure about sanity of the iOS part.
|
These files are not formatted correctly (see diff above): |
formatted using vscode
|
I had to run the formatters manually |
|
contours should never be null |
|
I observed that this doubles (13MB to 30MB) the output size of the APK. |
|
Hi @p30arena We haven't added this feature yet because we are currently focusing on integration testing. Once we implement those, it will be easier for us to add additional features to the plugin. Also, to avoid automatically increasing the size of the APK, we would not include the line Edit: Same for the line |
|
@bparrishMines |
bparrishMines
left a comment
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 the contribution!
Sorry for the delay. Everything looks good. I added a single comment.
Can you handle the merge conflicts, update the pubspec.yaml, and update the CHANGELOG? If not, I can also do these for you.
Are you still running into this error? Could it be from not including the dependency in the app. I'm not sure if you are using the example app or another. |
I merged the conflicts, Thanks |
This error is resolved |
bparrishMines
left a comment
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.
LGTM
I updated the version and added unit and integration tests.
Description
modified .gitignore to ommit some vscode related directories.
added contours to both android and iOS.
I'm not sure about sanity of the iOS part.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?