[Request][sensors_plus]: make package in pubspec.yaml the same with group in build.gradle

[zhyky]

Plugin

sensors_plus

Use case

Currently, sensors_plus plugin has different value between package in pubspec.yaml and group in build.gradle

in pubspec.yaml

flutter:
  plugin:
    platforms:
      android:
        package: dev.fluttercommunity.plus.sensors
        pluginClass: SensorsPlugin

in android/build.gradle

group 'io.flutter.plugins.sensors'
version '1.0-SNAPSHOT'

This will lead to strange behavior when checking tools written in dart read the package in pubspec.yaml

Proposal

Please make these two value same

[vbuberen]

Thanks for suggestion.

This will lead to strange behavior when checking tools written in dart read the package in pubspec.yaml

Do you have any examples of such strange behavior?

[zhyky]

Thanks for suggestion.

This will lead to strange behavior when checking tools written in dart read the package in pubspec.yaml

Do you have any examples of such strange behavior?

We have implemented a tool to run after flutter build aar to publish Plugin AAR to internal maven repository.

Before publish each AAR, the tool has a checking step to determinate whether it needs to be published.

The checking step use the package in pubspec.yaml, but the real output AAR's package is the group in build.gradle

All other Flutter plugin we are using have same value between package in pubspec.yaml and group in build.gradle, except sensors_plus