[connectivity_plus] eliminate indirect FFI dependency (#65) #66
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.
Same as
Moves the real implementation of connectivity_plus_linux behind a conditional export, instead of exporting a stub on platforms that don't support
dart:ffi
. This avoids build breakage in web projects that have transitive dependencies on connectivity_plus (and thus connectivity_plus_linux due to manual endorsement).This will no longer be necessary once flutter/flutter#52267 is fixed since only Linux builds will ever need to have a code-level dependency on connectivity_plus_linux.