Skip to content

Conversation

@ArgoZhang
Copy link
Member

@ArgoZhang ArgoZhang commented May 8, 2025

Link issues

fixes #5995

Summary By Copilot

This pull request refactors the fullscreen functionality across multiple components and services, simplifying the API by making the TargetId parameter optional. Key changes include updates to the FullScreenButton component, removal of unnecessary methods, and adjustments to unit tests to align with the new API.

Fullscreen Functionality Simplifications:

  • Updated :fullscreen selector in FullScreenButton.razor.scss to remove the :not(:root) pseudo-class, ensuring compatibility with modern fullscreen APIs.
  • Removed the TargetId parameter from FullScreenButton usage in Tab.razor, simplifying its invocation. [1] [2]
  • Updated FullScreenServiceExtensions to make the id parameter optional in the ToggleById method, enabling fullscreen toggling without explicitly providing an ID.

Code Cleanup:

  • Removed the GetIdByTabItem method from Tab.razor.cs as it is no longer needed due to the simplified fullscreen handling.
  • Simplified the OnFullScreen method in Tab.razor.cs by removing the dependency on GetIdByTabItem.

Unit Test Updates:

  • Adjusted FullScreenServiceTest to reflect the optional id parameter in ToggleById, removing the need to pass a specific ID during testing. [1] [2]

Regression?

  • Yes
  • No

Risk

  • High
  • Medium
  • Low

Verification

  • Manual (required)
  • Automated

Packaging changes reviewed?

  • Yes
  • No
  • N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

  • Doc is updated/provided or not needed
  • Demo is updated/provided or not needed
  • Merge the latest code from the main branch

Summary by Sourcery

Simplify fullscreen functionality across Tab and FullScreenButton components by making the target ID optional and removing unnecessary methods

New Features:

  • Simplified fullscreen API with optional target ID

Bug Fixes:

  • Fixed fullscreen selector compatibility with modern browser APIs

Enhancements:

  • Removed dependency on explicit target ID for fullscreen toggling
  • Simplified FullScreenButton and Tab component interactions

Chores:

  • Removed unnecessary methods like GetIdByTabItem
  • Updated unit tests to reflect new fullscreen API

@ArgoZhang ArgoZhang requested a review from Copilot May 8, 2025 06:55
@bb-auto bb-auto bot added the enhancement New feature or request label May 8, 2025
@sourcery-ai
Copy link
Contributor

sourcery-ai bot commented May 8, 2025

Reviewer's Guide

This pull request refactors the fullscreen invocation mechanism by making the TargetId parameter optional. This was achieved by modifying the ToggleById method in FullScreenServiceExtensions to accept a nullable id, removing the TargetId from FullScreenButton calls in Tab.razor, and deleting the GetIdByTabItem helper method along with its usage in Tab.razor.cs. Unit tests were updated to reflect this new optional parameter, and the fullscreen CSS selector in FullScreenButton.razor.scss was simplified.

File-Level Changes

Change Details Files
Made TargetId optional for fullscreen service and button.
  • Modified FullScreenServiceExtensions.ToggleById method to make the id parameter optional.
  • Removed TargetId attribute from FullScreenButton component usage.
  • Updated unit tests for FullScreenService.ToggleById to reflect the optional id parameter and removed explicit ID passing in tests for ToggleById and TestById method calls to it
src/BootstrapBlazor/Extensions/FullScreenServiceExtensions.cs
src/BootstrapBlazor/Components/Tab/Tab.razor
test/UnitTest/Services/FullScreenServiceTest.cs
Simplified Tab component logic for fullscreen.
  • Removed the GetIdByTabItem method.
  • Updated OnFullScreen method to call FullScreenService.ToggleById() without arguments, removing the dependency on GetIdByTabItem.
src/BootstrapBlazor/Components/Tab/Tab.razor.cs
Updated fullscreen CSS selector.
  • Changed CSS selector from :not(:root):fullscreen to :fullscreen for broader compatibility with modern fullscreen APIs.
src/BootstrapBlazor/Components/FullScreen/FullScreenButton.razor.scss

Assessment against linked issues

Issue Objective Addressed Explanation
#5995 Update FullScreen targetId

Possibly linked issues


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

@bb-auto bb-auto bot added this to the v9.6.0 milestone May 8, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR refactors the fullscreen functionality in several components and services by making the TargetId parameter optional and simplifying related code.

  • Updated the FullScreenButton component usage in Tab.razor to remove the TargetId parameter.
  • Modified FullScreenServiceExtensions to accept an optional id parameter.
  • Removed the GetIdByTabItem helper in Tab.razor.cs and updated unit tests to align with the new API.

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
test/UnitTest/Services/FullScreenServiceTest.cs Updated tests to invoke TestById without passing an ID, reflecting the updated API
src/BootstrapBlazor/Extensions/FullScreenServiceExtensions.cs Changed ToggleById to accept an optional id parameter
src/BootstrapBlazor/Components/Tab/Tab.razor.cs Removed GetIdByTabItem and updated OnFullScreen to call ToggleById with no parameter
src/BootstrapBlazor/Components/Tab/Tab.razor Updated FullScreenButton usage by removing the TargetId parameter
src/BootstrapBlazor/Components/FullScreen/FullScreenButton.razor.scss Adjusted the fullscreen CSS selector to match modern fullscreen API usage
Comments suppressed due to low confidence (1)

src/BootstrapBlazor/Components/Tab/Tab.razor.cs:1119

  • [nitpick] The 'context' parameter is no longer used in the OnFullScreen method. Consider removing it if it's not required by an interface or external contract to simplify the method signature.
private async Task OnFullScreen(ContextMenuItem item, object? context)

@codecov
Copy link

codecov bot commented May 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (417d198) to head (f3aeaf5).

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #5996   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          670       670           
  Lines        30624     30620    -4     
  Branches      4356      4355    -1     
=========================================
- Hits         30624     30620    -4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

sourcery-ai[bot]
sourcery-ai bot previously approved these changes May 8, 2025
Copy link
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @ArgoZhang - I've reviewed your changes - here's some feedback:

  • The Tab component's fullscreen buttons will now activate page-level fullscreen, a change from their previous behavior of targeting individual tab elements or the tab container.
Here's what I looked at during the review
  • 🟢 General issues: all looks good
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@ArgoZhang ArgoZhang merged commit 7d3ac79 into main May 8, 2025
3 checks passed
@ArgoZhang ArgoZhang deleted the fix-fs branch May 8, 2025 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(Tab): update FullScreen targetId

2 participants