smart_textfield 1.0.4 smart_textfield: ^1.0.4 copied to clipboard
TextField that can extract relevant information from the raw text input.
We analyzed this package 7 days ago, and awarded it 130 pub points (of a possible 160):
0/10 points: Provide a valid pubspec.yaml
Repository URL doesn't exist.
At the time of the analysis https://github.com/Yogi-7y/Project-Y/tree/main/packages/smart_textfield
was unreachable. Make sure that the website is reachable via HEAD
requests.
Failed to verify repository URL.
Please provide a valid repository
URL in pubspec.yaml
, such that:
repository
can be cloned,- a clone of the repository contains a
pubspec.yaml
, which:,- contains
name: smart_textfield
, - contains a
version
property, and, - does not contain a
publish_to
property.
- contains
Repository has no matching pubspec.yaml
with name: smart_textfield
.
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
24 out of 126 API elements (19.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: smart_textfield
, smart_textfield.DateTimeSelectionItem
, smart_textfield.DateTimeSelectionItem.DateTimeSelectionItem
, smart_textfield.SelectionMenu
, smart_textfield.SelectionMenu.SelectionMenu
.
10/10 points: Package has an example
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.
40/50 points: code has no errors, warnings, lints, or formatting issues
Found 11 issues. Showing the first 2:
INFO: Statements in an if should be enclosed in a block.
lib/src/module/domain/entity/tokenizer.dart:66:9
╷
66 │ ┌ _tokens.add(Token<T>(
67 │ │ prefix: prefix,
68 │ │ rawValue: '$prefix${value.stringValue}',
69 │ │ displayValue: value.stringValue,
70 │ │ value: value,
71 │ │ isHighlighted: true,
72 │ │ offset: TokenOffset(
73 │ │ start: _match.start,
74 │ │ end: _match.end,
75 │ │ ),
76 │ └ ));
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/module/domain/entity/tokenizer.dart
INFO: Statements in an if should be enclosed in a block.
lib/src/module/domain/use_case/smart_textfield_use_case.dart:63:7
╷
63 │ ┌ return [
64 │ │ Token<TokenableString>(
65 │ │ prefix: '',
66 │ │ rawValue: text,
67 │ │ displayValue: text,
68 │ │ value: TokenableString(text),
69 │ │ offset: TokenOffset(
70 │ │ start: 0,
71 │ │ end: text.length,
72 │ │ ),
73 │ │ ),
74 │ └ ];
╵
To reproduce make sure you are using the lints_core and run flutter analyze lib/src/module/domain/use_case/smart_textfield_use_case.dart
10/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
collection |
^1.18.0 |
1.18.0 | 1.19.0 |
flutter |
flutter |
0.0.0 | 0.0.0 |
flutter_portal |
^1.1.4 |
1.1.4 | 1.1.4 |
meta |
^1.10.0 |
1.15.0 | 1.15.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
characters |
- | 1.3.0 | 1.3.0 |
material_color_utilities |
- | 0.11.1 | 0.12.0 |
sky_engine |
- | 0.0.99 | 0.0.99 |
vector_math |
- | 2.1.4 | 2.1.4 |
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.12
, Flutter 3.24.2
, Dart 3.5.2
.
Check the analysis log for details.