这是indexloc提供的服务,不要输入任何密码
Skip to content

feat(router): optional router in AddTaskButton #4176

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

Merged
merged 5 commits into from
Jul 15, 2025

Conversation

rafalmaksymiuk
Copy link
Contributor

@rafalmaksymiuk rafalmaksymiuk commented Jul 14, 2025

AddTaskButton is now accepting routerDisabled prop and acts accordingly using routing handlers instead of ReactRouter. Tests were converted to RTL and expanded.

Summary by CodeRabbit

  • New Features

    • Improved sidebar navigation flexibility in the Add Task button, supporting both standard routing and an alternative internal navigation handler.
  • Tests

    • Updated tests to use React Testing Library for more accurate user interaction simulation.
    • Added new tests to ensure correct behavior when the alternative navigation handler is used.

@rafalmaksymiuk rafalmaksymiuk requested review from a team as code owners July 14, 2025 09:46
Copy link

coderabbitai bot commented Jul 14, 2025

"""

Walkthrough

The AddTaskButton component was updated to support an alternative navigation mechanism using new props, allowing navigation state to be managed via either React Router or an internal handler. Corresponding tests were refactored to use React Testing Library and expanded to cover the new navigation logic.

Changes

File(s) Change Summary
src/elements/content-sidebar/AddTaskButton.js Added optional props for internal navigation, updated click handler to conditionally use router or handler.
src/elements/content-sidebar/tests/AddTaskButton.test.js Refactored tests to React Testing Library, added tests for internal navigation handler and routerDisabled.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant AddTaskButton
    participant Router
    participant InternalNavHandler

    User->>AddTaskButton: Clicks menu item
    alt routerDisabled is true and handler exists
        AddTaskButton->>InternalNavHandler: handle(internalSidebarNavigation + open: true, true)
    else
        AddTaskButton->>Router: history.replace({ state: { open: true } })
    end
Loading

Possibly related PRs

Suggested reviewers

  • jankowiakdawid
  • greg-in-a-box

Poem

A button for tasks, now smarter and keen,
Chooses its path—internal or routine.
With tests refactored, clicks are now clear,
Navigation handled, no need to fear!
🐇✨
Sidebar or router, both work just fine—
The code hops ahead, right on the line!
"""


📜 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 3266c3f and 485137e.

📒 Files selected for processing (1)
  • src/elements/content-sidebar/__tests__/AddTaskButton.test.js (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/elements/content-sidebar/tests/AddTaskButton.test.js
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: lint_test_build
  • GitHub Check: Summary
✨ Finishing Touches
  • 📝 Generate Docstrings

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.

kajarosz
kajarosz previously approved these changes Jul 14, 2025
jankowiakdawid
jankowiakdawid previously approved these changes Jul 15, 2025
mergify bot added a commit that referenced this pull request Jul 15, 2025
Copy link
Contributor

mergify bot commented Jul 15, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You can check the last failing draft PR here: #4181.

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@rafalmaksymiuk rafalmaksymiuk dismissed stale reviews from jankowiakdawid and kajarosz via 3266c3f July 15, 2025 11:23
jankowiakdawid
jankowiakdawid previously approved these changes Jul 15, 2025
kajarosz
kajarosz previously approved these changes Jul 15, 2025
@rafalmaksymiuk rafalmaksymiuk dismissed stale reviews from kajarosz and jankowiakdawid via 485137e July 15, 2025 13:47
mergify bot added a commit that referenced this pull request Jul 15, 2025
Copy link
Contributor

mergify bot commented Jul 15, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You can check the last failing draft PR here: #4183.

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@greg-in-a-box
Copy link
Contributor

@Mergifyio refresh

Copy link
Contributor

mergify bot commented Jul 15, 2025

refresh

✅ Pull request refreshed

mergify bot added a commit that referenced this pull request Jul 15, 2025
Copy link
Contributor

mergify bot commented Jul 15, 2025

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You can check the last failing draft PR here: #4184.

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@mergify mergify bot merged commit 90537b4 into box:master Jul 15, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants