🧹 Fix code quality warnings

[NITISH-R-G]

🧹 Fix code quality warnings

🎯 What:

• Added header: "" to l10n.yaml to prevent generation of // ignore: unused_import.
• Excluded lib/l10n/** from analysis_options.yaml to hide unused import lints.
• Removed // ignore: unused_field and cleaned up unused _ref fields in webrtc_voice_call_service.dart and family_circle_service.dart.
• Fixed // ignore: discarded_futures in first_aid_screen.dart by using unawaited.

💡 Why:

• Avoid suppressing lint rules using // ignore: comments. Fix them using structural solutions or localized exclusions.

✅ Verification:

• Ran dart analyze (0 issues found).
• Ran flutter test (all pass).

✨ Result:

• A cleaner codebase fully compliant with production-grade analysis standards.

---

PR created automatically by Jules for task 14395611442845637226 started by @NITISH-R-G

Summary by Sourcery

Improve code quality by addressing linter warnings through structural changes in services, localization setup, and first aid UI rather than suppressing them with ignore comments.

Bug Fixes:

• Resolve discarded future handling in first aid screen by wrapping the call in unawaited instead of ignoring the lint.

Enhancements:

• Clean up unused Riverpod Ref fields and related ignore comments from voice call and family circle services.
• Configure localization generation and analysis to avoid unused import warnings by adding a header in l10n.yaml, excluding lib/l10n/** from analyzer, and removing generated ignore comments.

Build:

• Update analysis_options.yaml to exclude localization files from static analysis.

Documentation:

• Add a Jules bolt note documenting the approach for fixing discarded_futures lint using unawaited.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[github-actions]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a8ede313-e280-44c9-a0b6-aa4750345f23

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR removes inline lint suppressions by structurally resolving the underlying issues: localization generation now avoids emitting unused imports and is excluded from analysis, unused Riverpod Ref fields are removed while preserving constructor signatures, an unawaited future is explicitly wrapped with unawaited(), and a small Jules note documents the discarded_futures fix.

Sequence diagram for unawaited FirstAidStore call in first aid screen

sequenceDiagram
    actor User
    participant FirstAidScreenState

    User ->> FirstAidScreenState: onQuerySubmitted(query)
    FirstAidScreenState ->> FirstAidScreenState: unawaited(FirstAidStore.getVerifiedAdvice(query))

Loading

File-Level Changes

Change	Details	Files
Clean up unused Riverpod Ref fields and related ignores in services.	Change WebRtcVoiceCallService constructor to take Ref positionally without storing it, removing the unused _ref field and its ignore comment while keeping bootstrap behavior. Remove the unused _ref field assignment and declaration in FamilyCircleService, relying on the constructor parameter solely for call-site compatibility.	lib/services/webrtc_voice_call_service.dart lib/services/family_circle_service.dart
Handle intentionally unawaited futures without suppressing lints.	Replace the discarded_futures ignore in FirstAidScreen with an explicit unawaited(FirstAidStore.getVerifiedAdvice(query)) call to document the unawaited future.	lib/ui/first_aid_screen.dart
Adjust localization generation and analysis config to avoid unused_import lints structurally.	Add header: "" to l10n.yaml so generated localization files no longer include the unused_import ignore header. Exclude lib/l10n/** from analyzer in analysis_options.yaml so generated code is not linted for unused imports. Remove now-unnecessary // ignore: unused_import comments from generated app_localizations_*.dart files.	l10n.yaml analysis_options.yaml lib/l10n/app_localizations_bn.dart lib/l10n/app_localizations_en.dart lib/l10n/app_localizations_hi.dart lib/l10n/app_localizations_mr.dart lib/l10n/app_localizations_ta.dart lib/l10n/app_localizations_te.dart
Document the lint fix approach for discarded_futures in Jules metadata.	Add a Jules bolt note describing the learning and action taken to fix discarded_futures via unawaited instead of ignore comments.	.jules/bolt.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.