swift_composer 0.2.0

swift_composer: ^0.2.0 copied to clipboard

10/10 points: Provide a valid pubspec.yaml

5/5 points: Provide a valid README.md

5/5 points: Provide a valid CHANGELOG.md

10/10 points: Package has an example

• Found example at: example/main.dart

0/10 points: Failed to run dartdoc

• dartdoc failed with:

exitCode: 255
stdout: Documenting swift_composer...
Initialized dartdoc with 670 libraries in 59.7 seconds
Generating docs for library swift_composer from package:swift_composer/swift_composer.dart...
Generating docs for library swift_composer from package:swift_composer/swift_generator.dart...
Documented 2 public libraries in 1.2 seconds
stderr:   warning: swift_composer has no library level documentation comments, from swift_composer: (file:///tmp/pub-dartlang-dartdocAMYKXR/pkg/lib/swift_composer.dart:1:9)
  warning: swift_composer has no library level documentation comments, from swift_composer: (file:///tmp/pub-dartlang-dartdocAMYKXR/pkg/lib/swift_generator.dart:1:9)
  error: failed to write file at: swift_composer/swift_composer-library.html
    for symbol swift_composer: (file:///tmp/pub-dartlang-dartdocAMYKXR/pkg/lib/swift_generator.dart:1:9)
    conflicting with file already generated by swift_composer: (file:///tmp/pub-dartlang-dartdocAMYKXR/pkg/lib/swift_composer.dart:1:9)
            Dartdoc generates a path and filename to write to for each symbol.
            swift_composer conflicts with another symbol in the generated path, and
            therefore can not be written out.  Changing the name, library name, or
            class name (if appropriate) of one of the conflicting items can resolve
            the conflict.   Alternatively, use the @nodoc tag in one symbol's
            documentation comments to hide it.
Found 2 warnings and 1 error.
Unhandled exception:
encountered 1 errors
#0      Dartdoc.generateDocs (package:dartdoc/dartdoc.dart:247:9)
<asynchronous suspension>
#1      main (file:///project/pkg/pub_dartdoc/bin/pub_dartdoc.dart:22:19)
<asynchronous suspension>

20/20 points: Supports 2 of 2 possible platforms (native, js)

20/30 points: code has no errors, warnings, lints, or formatting issues

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

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

Found 5 issues. Showing the first 2:

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

0/20 points: Package does not opt in to null safety.