Skip to content

fix: recognize Dart and Flutter build output with project context - #6

Open
QIU-Guanzong wants to merge 1 commit into
Juuzoe:mainfrom
QIU-Guanzong:fix/flutter-build
Open

QIU-Guanzong wants to merge 1 commit into
Juuzoe:mainfrom
QIU-Guanzong:fix/flutter-build

Conversation

@QIU-Guanzong

Copy link
Copy Markdown

Classifies build/ as Dart/Flutter output only when its parent contains pubspec.yaml. A sibling lockfile raises confidence; a lockfile alone cannot claim a generic build directory. A real-filesystem test covers locked/unlocked Dart projects, the nested Android Gradle build and an unrelated directory.

Closes #1.

Validation: cargo fmt --all and cargo test passed (314 tests including doc tests). The required cargo clippy --all-targets --all-features -- -D warnings was run but hits the unchanged macOS casts reported separately in #5; reproduced on the unmodified base. No cleanup implementation changes.

Prepared with AI assistance; tests were run locally on macOS arm64 / Rust 1.88.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Flutter's build/ is not detected, though .dart_tool beside it is

1 participant