chore: ignore auto-generated files (*.g.dart, *.mocks.dart) #417
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was an inconsistency in how we handled generated files:
*.g.dartand*.mocks.dartfiles (since fix: add missing build_runner step to flutter.yml workflow #375)Example: A change to
Settingsclass generates +30 lines inmocks.mocks.dartthat pollute the PR diff.This PR completes the work from #375 by adding generated files to
.gitignore:Before:
After:
.gitignore(not committed)dart run build_runner build -dThis aligns with Flutter ecosystem standards (Flutter SDK, Riverpod, Provider all do this).
After pulling this PR, all developers must run:
Git will delete the generated files from your workspace (since they're now untracked). This command regenerates them locally so the app compiles.
You only need to do this once after pulling this PR. The README and CONTRIBUTING.md now document this as a mandatory setup step for new contributors.
Summary by CodeRabbit
Documentation
Chores
✏️ Tip: You can customize this high-level summary in your review settings.