Hi! This is a proposal to merge the ffi-wrapper branch into main. It looks like most development moved to this branch? I think it would be useful to work against / send PRs to the default branch.
Note that I did not add any additional commits to the ffi-wrapper branch - this is just a straight merge of that branch into main.
cc @craiglabenz @PaulTR
Related Issues
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. Updating the pubspec.yaml and changelogs is not required.
[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (melos run analyze) does not report any problems on my PR.
Description
Hi! This is a proposal to merge the
ffi-wrapperbranch intomain. It looks like most development moved to this branch? I think it would be useful to work against / send PRs to the default branch.Note that I did not add any additional commits to the
ffi-wrapperbranch - this is just a straight merge of that branch into main.cc @craiglabenz @PaulTR
Related Issues
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. Updating thepubspec.yamland changelogs is not required.///).melos run 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?