ab_testing_firebase 1.0.0+1 ab_testing_firebase: ^1.0.0+1 copied to clipboard
Extends ab_testing_core to support remote A/B testing with Firebase Remote Config.
3
likes
40/ 140
pub points
35%
popularity
We analyzed this package 3 hours ago, and awarded it 40 pub points (of a possible 140):
10/10 points: Provide a valid pubspec.yaml
Issue tracker URL doesn't exist.
At the time of the analysis https://github.com/programmierbar/ab_testing/issues
was unreachable. Make sure that the website is reachable via HEAD
requests.
5/5 points: Provide a valid README.md
5/5 points: Provide a valid CHANGELOG.md
10/10 points: Use an OSI-approved license
Detected license: MIT
.
0/10 points: 20% or more of the public API has dartdoc comments
Dependency resolution failed, unable to run dartdoc
.
0/10 points: Package has an example
No example found.
See package layout guidelines on how to add an example.
0/20 points: Platform support detection failed
Could not determine supported platforms as package resolution failed.
Run dart pub get
for more information.
0/50 points: code has no errors, warnings, lints, or formatting issues
- Running
dart pub outdated
failed with the following output:
Because firebase_remote_config >=0.9.0-dev.0 depends on flutter from sdk which doesn't exist (could not find package flutter in the Flutter SDK), firebase_remote_config >=0.9.0-dev.0 is forbidden.
So, because ab_testing_firebase depends on firebase_remote_config ^4.0.0, version solving failed.
0/10 points: All of the package dependencies are supported in the latest version
- Could not run
dart pub outdated
:dart pub get
failed:
OUT:
Resolving dependencies...
ERR:
Because firebase_remote_config >=0.9.0-dev.0 depends on flutter from sdk which doesn't exist (could not find package flutter in the Flutter SDK), firebase_remote_config >=0.9.0-dev.0 is forbidden.
So, because ab_testing_firebase depends on firebase_remote_config ^4.0.0, version solving failed.
10/10 points: Package supports latest stable Dart and Flutter SDKs
Analyzed with Pana 0.22.3
, Dart 3.3.3
.
Check the analysis log for details.