Skip to content

Dev - #13

Merged
lizy-coding merged 18 commits into
masterfrom
dev
Aug 22, 2026
Merged

Dev#13
lizy-coding merged 18 commits into
masterfrom
dev

Conversation

@lizy-coding

Copy link
Copy Markdown
Owner

No description provided.

Replace the machine-specific ../../../flutterguard path dependency with a
pinned git ref (9f9be84, flutterguard_cli 0.7.1) so pub resolution and CI
no longer depend on a sibling checkout. AI docs regenerated to match.
tool/generate_agent_indexes.js is now the only hand-edited source for module
registration; writeRouteTable() emits apps/flutter_forge/lib/app/router/
app_route_table.dart (DO-NOT-EDIT header). validate_agent_docs.js asserts
generate-source == AI_MODULE_INDEX consistency and that every module route is
present in the generated route table. Proven single-source via a throwaway
dry-run (removing one module drops it from both index and route table).
dio 5.11.0 adds DioExceptionType.transformTimeout, making the error
interceptor switch non-exhaustive. Local lock pinned 5.9.2 so the error only
surfaced on remote/CI packaging. Add the explicit case and bump the constraint
to ^5.11.0 so local == remote (no version-drift landmine). Unit test asserts
every DioExceptionType value, including transformTimeout, is forwarded.
Run dart fix --apply in apps/flutter_forge to clear the 192 info-level
diagnostics (prefer_const_constructors, prefer_const_literals_to_create_immutables,
prefer_final_fields) that made bare flutter analyze exit non-zero. Manually
migrate ReorderableListView onReorder -> onReorderItem and drop the now-redundant
newIndex adjustment (the new callback pre-adjusts for the removed item).
No behavior or layout changes.
Remove --no-fatal-infos --no-fatal-warnings so info/warning diagnostics fail
the gate exactly like remote packaging would. Now that the 192-info backlog is
cleared, local acceptance matches remote packaging behavior permanently.
Remove the FlutterGuard scan step (it ran from the repo root where no lib/
exists and always failed with an empty match) along with the now-dead pinned
checkout + sibling-mv steps. flutterguard_cli remains a pinned git dev
dependency and is still enforced by the local quality_gate.sh.
@lizy-coding
lizy-coding merged commit c02f523 into master Aug 22, 2026
2 checks passed
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.

1 participant