dyte_core_platform_interface 0.4.5 copy "dyte_core_platform_interface: ^0.4.5" to clipboard
dyte_core_platform_interface: ^0.4.5 copied to clipboard

A common platform interface for the dyte_core plugin.

0
likes
120/ 160
pub points
33%
popularity

We analyzed this package 13 days ago, and awarded it 120 pub points (of a possible 160):

failed
Follow Dart file conventions
20 / 30trigger folding of the section

0/10 points: Provide a valid pubspec.yaml

The package description is too short.

Add more detail to the description field of pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.

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.

failed
Provide documentation
0 / 20trigger folding of the section

0/10 points: 20% or more of the public API has dartdoc comments

63 out of 917 API elements (6.9 %) have documentation comments.

Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API. Document at least 20% of the public API elements.

To highlight public API members missing documentation consider enabling the public_member_api_docs lint.

Some symbols that are missing documentation: dyte_core_platform_interface, dyte_core_platform_interface.AudioDeviceType, dyte_core_platform_interface.AudioDeviceType.deviceType, dyte_core_platform_interface.AudioDeviceType.displayName, dyte_core_platform_interface.AudioDeviceType.toMap.

0/10 points: Package has an example

No example found.

See package layout guidelines on how to add an example.

OK
Platform support
20 / 20trigger folding of the section

20/20 points: Supports 6 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)

  • ✓ Android

  • ✓ iOS

  • ✓ Windows

  • ✓ Linux

  • ✓ macOS

  • ✓ Web

0/0 points: WASM compatibility

This package is compatible with runtime wasm, and will be rewarded additional points in a future version of the scoring model.

See https://dart.dev/web/wasm for details.

partial
Pass static analysis
40 / 50trigger folding of the section

40/50 points: code has no errors, warnings, lints, or formatting issues

INFO: 'onPresentRequestAccepted' is deprecated and shouldn't be used. Use onParticipantStartedPresenting instead.

lib/src/method_channels/dyte_stage_listener_channel.dart:87:34

   ╷
87 │         case DyteStageEventsName.onPresentRequestAccepted:
   │                                  ^^^^^^^^^^^^^^^^^^^^^^^^
   ╵

To reproduce make sure you are using the lints_core and run flutter analyze lib/src/method_channels/dyte_stage_listener_channel.dart

INFO: 'onPresentRequestAccepted' is deprecated and shouldn't be used. use onParticipantStartedPresenting() instead.

lib/src/method_channels/dyte_stage_listener_channel.dart:95:21

   ╷
95 │             element.onPresentRequestAccepted(participant);
   │                     ^^^^^^^^^^^^^^^^^^^^^^^^
   ╵

To reproduce make sure you are using the lints_core and run flutter analyze lib/src/method_channels/dyte_stage_listener_channel.dart

OK
Support up-to-date dependencies
40 / 40trigger folding of the section

10/10 points: All of the package dependencies are supported in the latest version

Package Constraint Compatible Latest
flutter flutter 0.0.0 0.0.0
focus_detector_v2 ^3.1.0+1 3.1.0+1 3.1.0+1
plugin_platform_interface ^2.1.8 2.1.8 2.1.8
Transitive dependencies
Package Constraint Compatible Latest
characters - 1.3.0 1.3.1
collection - 1.18.0 1.19.1
material_color_utilities - 0.11.1 0.12.0
meta - 1.15.0 1.16.0
sky_engine - 0.0.99 0.0.99
vector_math - 2.1.4 2.1.4
visibility_detector - 0.4.0+2 0.4.0+2

To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides.

10/10 points: Package supports latest stable Dart and Flutter SDKs

20/20 points: Compatible with dependency constraint lower bounds

pub downgrade does not expose any static analysis error.

Analyzed with Pana 0.22.15, Flutter 3.24.5, Dart 3.5.4.

Check the analysis log for details.