ff_annotation_route 10.1.0
ff_annotation_route: ^10.1.0 copied to clipboard

Published 2 months ago •

fluttercandies.comDart 3 compatible

SDKDart

PlatformLinux macOS Windows

→

Metadata

Provide a route generator to create route map quickly by annotations.

More...

likes

110/ 160

pub points

59%

popularity

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

Follow Dart file conventions

30 / 30

10/10 points: Provide a valid `pubspec.yaml`

Issue tracker URL doesn't exist.

At the time of the analysis https://github.com/fluttercandies/ff_annotation_route/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.

Provide documentation

10 / 20

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

0 out of 2 API elements (0.0 %) 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: ff_annotation_route, ff_annotation_route.generate.

10/10 points: Package has an example

Platform support

20 / 20

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

✓ Windows
✓ Linux
✓ macOS

These platforms are not supported:

Package does not support platform `Android`.

Because:

package:ff_annotation_route/ff_annotation_route.dart that imports:
package:build_runner_core/build_runner_core.dart that declares support for platforms: Windows, Linux, macOS.

Package does not support platform `iOS`.

Because:

package:ff_annotation_route/ff_annotation_route.dart that imports:
package:build_runner_core/build_runner_core.dart that declares support for platforms: Windows, Linux, macOS.

Package does not support platform `Web`.

Because:

package:ff_annotation_route/ff_annotation_route.dart that imports:
package:build_runner_core/build_runner_core.dart that declares support for platforms: Windows, Linux, macOS.

0/0 points: WASM compatibility

Package not compatible with runtime wasm

Because:

package:ff_annotation_route/ff_annotation_route.dart that imports:
package:ff_annotation_route/src/utils/git_package_handler.dart that imports:
package:io/ansi.dart that imports:
package:io/src/ansi_code.dart that imports:
dart:io

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

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

Pass static analysis

40 / 50

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

Found 3 issues. Showing the first 2:

INFO: 'FFArgumentImport' is deprecated and shouldn't be used. Use FFAutoImport instead.

lib/src/route_generator/fast_route_generator.dart:70:32

   ╷
70 │                         typeOf<FFArgumentImport>().toString() ||
   │                                ^^^^^^^^^^^^^^^^
   ╵

To reproduce make sure you are using the lints_core and run dart analyze lib/src/route_generator/fast_route_generator.dart

INFO: 'FFArgumentImport' is deprecated and shouldn't be used. Use FFAutoImport instead.

lib/src/route_generator/route_generator.dart:30:35

   ╷
30 │     const TypeChecker.fromRuntime(FFArgumentImport);
   │                                   ^^^^^^^^^^^^^^^^
   ╵

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

Support up-to-date dependencies

10 / 40

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

Package	Constraint	Compatible	Latest
`analyzer`	`^5.0.0`	5.13.0	7.0.0
`args`	`^2.3.1`	2.6.0	2.6.0
`build_runner_core`	`^7.2.3`	7.3.2	7.3.2
`collection`	`^1.16.0`	1.19.1	1.19.1
`crypto`	`^3.0.2`	3.0.6	3.0.6
`dart_style`	`^2.2.3`	2.3.2	2.3.7
`ff_annotation_route_core`	`^2.1.0`	2.1.0	2.1.0
`io`	`^1.0.3`	1.0.4	1.0.4
`meta`	`^1.7.0`	1.16.0	1.16.0
`path`	`^1.8.1`	1.9.1	1.9.1
`pub_cache`	`^0.3.1`	0.3.2	0.3.2
`source_gen`	`^1.2.5`	1.5.0	1.5.0
`yaml`	`^3.1.1`	3.1.2	3.1.2

Transitive dependencies

Package	Constraint	Compatible	Latest
`_fe_analyzer_shared`	-	61.0.0	77.0.0
`async`	-	2.12.0	2.12.0
`build`	-	2.4.1	2.4.1
`build_config`	-	1.1.1	1.1.1
`build_resolvers`	-	2.4.2	2.4.2
`checked_yaml`	-	2.0.3	2.0.3
`convert`	-	3.1.2	3.1.2
`file`	-	7.0.1	7.0.1
`glob`	-	2.1.2	2.1.2
`graphs`	-	2.3.2	2.3.2
`json_annotation`	-	4.9.0	4.9.0
`logging`	-	1.3.0	1.3.0
`package_config`	-	2.1.0	2.1.0
`pool`	-	1.5.1	1.5.1
`pub_semver`	-	2.1.4	2.1.4
`pubspec_parse`	-	1.3.0	1.3.0
`source_span`	-	1.10.0	1.10.0
`stack_trace`	-	1.12.0	1.12.0
`stream_transform`	-	2.1.0	2.1.0
`string_scanner`	-	1.4.0	1.4.0
`term_glyph`	-	1.2.1	1.2.1
`timing`	-	1.0.1	1.0.1
`typed_data`	-	1.4.0	1.4.0
`watcher`	-	1.1.0	1.1.0

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

The constraint `^5.0.0` on analyzer does not support the stable version `6.0.0`.

Try running dart pub upgrade --major-versions analyzer to update the constraint.

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

0/20 points: Compatible with dependency constraint lower bounds

downgrade analysis failed failed with 18 errors:

UNDEFINED_GETTER - lib/src/route_generator/fast_route_generator.dart:96:56 - The getter 'name' isn't defined for the type 'ClassDeclaration'.
FOR_IN_OF_INVALID_ELEMENT_TYPE - lib/src/route_generator/fast_route_generator.dart:218:22 - The type 'NodeListImpl
UNDEFINED_GETTER - lib/src/route_generator/fast_route_generator.dart:283:40 - The getter 'name' isn't defined for the type 'FunctionDeclaration'.

Run dart pub downgrade and then dart analyze to reproduce the above problem.

You may run dart pub upgrade --tighten to update your dependency constraints, see dart.dev/go/downgrade-testing for details.

Analyzed with Pana 0.22.15, Dart 3.5.4.

Check the analysis log for details.