Skip to content

Add useCupertinoTabController hook for automatic disposal of CupertinoTabController #475

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Erengun
Copy link

@Erengun Erengun commented Jun 17, 2025

Hi Remi 👋

Resolves #222

Introduce a new hook for managing the lifecycle of CupertinoTabController, ensuring it disposes automatically. Include tests to verify its functionality and correct behavior.

no towel required. 🪐

Summary by CodeRabbit

  • New Features

    • Introduced a new hook for managing a Cupertino tab controller with support for setting the initial tab index.
  • Tests

    • Added comprehensive widget tests to verify the behavior and properties of the new Cupertino tab controller hook.

Copy link

coderabbitai bot commented Jun 17, 2025

Walkthrough

A new Flutter hook, useCupertinoTabController, is introduced to manage a CupertinoTabController instance with lifecycle support. The hook is integrated into the hooks library, and comprehensive widget tests are added to verify its behavior, parameter handling, and debug diagnostics.

Changes

File(s) Change Summary
packages/flutter_hooks/lib/src/cupertino_tab_controller.dart Added useCupertinoTabController hook and supporting private hook/state classes.
packages/flutter_hooks/lib/src/hooks.dart Added import for CupertinoTabController and part directive for the new hook implementation.
packages/flutter_hooks/test/use_cupertino_tab_controller_test.dart Added widget tests for useCupertinoTabController, covering construction, identity, and debug.

Sequence Diagram(s)

sequenceDiagram
    participant Widget
    participant HookBuilder
    participant useCupertinoTabController
    participant CupertinoTabController

    Widget->>HookBuilder: Build widget tree
    HookBuilder->>useCupertinoTabController: Invoke hook (with initialIndex)
    useCupertinoTabController->>CupertinoTabController: Instantiate (if first build)
    useCupertinoTabController-->>HookBuilder: Return controller instance
    HookBuilder-->>Widget: Provide controller for use
    Widget-->>CupertinoTabController: Use controller as needed
Loading

Assessment against linked issues

Objective Addressed Explanation
Add useCupertinoTabController hook that manages a CupertinoTabController instance (#222)

Suggested reviewers

  • rrousselGit

Poem

In the garden of hooks, a new sprout appears,
For Cupertino tabs, it now steers!
With tests that ensure it’s robust and neat,
This controller’s lifecycle is now complete.
A hop, a wiggle, a code rabbit’s cheer—
Flutter’s tabs just got easier here!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 97a3bef and 470968f.

📒 Files selected for processing (1)
  • packages/flutter_hooks/test/use_cupertino_tab_controller_test.dart (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/flutter_hooks/test/use_cupertino_tab_controller_test.dart

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (4)
packages/flutter_hooks/lib/src/hooks.dart (1)

3-4: Minor style inconsistency in multi-line import

The previous multi-line import 'package:flutter/material.dart' statement keeps the URI and the show combinator on the same physical line (see lines 6-17). For consistency, consider collapsing lines 3-4 into one line or applying the same line-break pattern to both imports.

packages/flutter_hooks/lib/src/cupertino_tab_controller.dart (2)

20-30: Parameter not included in keys – check desire to recreate controller on param change

initialIndex is forwarded to the hook state but not added to the keys list.
If a parent widget rebuilds with a different initialIndex, the existing CupertinoTabController will be reused instead of creating a fresh one. That is usually correct (developers can call controller.index = … instead), but double-check that this matches the intended behaviour for your API.

 return use(
   _CupertinoTabControllerHook(
       initialIndex: initialIndex,
-      keys: keys,
+      keys: keys ?? <Object?>[initialIndex],
   ),
 );

35-43: Missing super.dispose() call is harmless but adds clarity

HookState.dispose is currently a no-op, so omitting super.dispose() is safe.
Calling it anyway improves forward-compatibility and mirrors patterns elsewhere in the codebase.

 @override
 void dispose() {
   controller.dispose();
+  super.dispose();
 }
packages/flutter_hooks/test/use_cupertino_tab_controller_test.dart (1)

33-34: Typo in group description

useCupertinoCupertinoCupertinoTabController has the word Cupertino repeated three times.

-group('useCupertinoCupertinoCupertinoTabController', () {
+group('useCupertinoTabController', () {
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e802dd3 and 97a3bef.

📒 Files selected for processing (3)
  • packages/flutter_hooks/lib/src/cupertino_tab_controller.dart (1 hunks)
  • packages/flutter_hooks/lib/src/hooks.dart (2 hunks)
  • packages/flutter_hooks/test/use_cupertino_tab_controller_test.dart (1 hunks)

Comment on lines +1 to +7
import 'package:flutter/cupertino.dart';
import 'package:flutter/foundation.dart';
import 'package:flutter_hooks/src/framework.dart';
import 'package:flutter_hooks/src/hooks.dart';

import 'mock.dart';

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Tests fail to compile – missing flutter_test import & unused mock.dart

testWidgets, equalsIgnoringHashCodes, and other testing utilities live in package:flutter_test/flutter_test.dart, which is not imported.
mock.dart is imported but never referenced, causing an “unused import” lint.

-import 'package:flutter/foundation.dart';
-import 'package:flutter_hooks/src/framework.dart';
-import 'package:flutter_hooks/src/hooks.dart';
-import 'mock.dart';
+import 'package:flutter_test/flutter_test.dart';
+import 'package:flutter_hooks/flutter_hooks.dart';

(Remove mock.dart unless it is actually used.)

This change lets the suite compile and removes needless internal-API exposure.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
import 'package:flutter/cupertino.dart';
import 'package:flutter/foundation.dart';
import 'package:flutter_hooks/src/framework.dart';
import 'package:flutter_hooks/src/hooks.dart';
import 'mock.dart';
import 'package:flutter/cupertino.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:flutter_hooks/flutter_hooks.dart';
🤖 Prompt for AI Agents
In packages/flutter_hooks/test/use_cupertino_tab_controller_test.dart at lines 1
to 7, the test file is missing the import for
package:flutter_test/flutter_test.dart, which provides essential testing
utilities like testWidgets and equalsIgnoringHashCodes. Add this import to
enable the tests to compile. Also, remove the import of mock.dart since it is
not used anywhere in the file to avoid unused import lint warnings and reduce
unnecessary internal API exposure.

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.

Add useCupertinoTabController
1 participant