Skip to content

docs: Update flutter full-screen API and event listeners#96

Merged
Balamurugan-Testpress merged 2 commits intomainfrom
doc_flutter_sdk_fullscreen_api
Mar 20, 2026
Merged

docs: Update flutter full-screen API and event listeners#96
Balamurugan-Testpress merged 2 commits intomainfrom
doc_flutter_sdk_fullscreen_api

Conversation

@Balamurugan-Testpress
Copy link
Copy Markdown
Contributor

  • Add enterFullScreen() and exitFullScreen() methods
  • Document onBeforeFullScreenEnter and onBeforeFullScreenExit callbacks

- Add enterFullScreen() and exitFullScreen() methods
- Document onBeforeFullScreenEnter and onBeforeFullScreenExit callbacks
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the Flutter SDK documentation by adding comprehensive guides for new fullscreen functionalities. It provides clear instructions and examples for programmatically entering and exiting fullscreen mode, as well as for utilizing new callbacks to react to fullscreen state transitions. These updates aim to improve the developer experience by offering more control and observability over the player's fullscreen behavior.

Highlights

  • Fullscreen API Methods: Added documentation for enterFullScreen() and exitFullScreen() methods, allowing programmatic control over fullscreen mode in the Flutter SDK.
  • Fullscreen Event Listeners: Documented onBeforeFullScreenEnter and onBeforeFullScreenExit callbacks, enabling developers to listen for fullscreen state changes.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the documentation for the Flutter SDK to include new fullscreen APIs and event listeners. My review focuses on improving the code examples for clarity and consistency with Dart's conventions. I've suggested using null-safe operators for controller access to prevent potential runtime errors and recommended aligning method and property names with the lowerCamelCase convention for better code quality and readability.

Comment thread docs/mobile-sdk/flutter-sdk/player-events.md Outdated
Comment thread docs/mobile-sdk/flutter-sdk/player-methods.md
@Balamurugan-Testpress Balamurugan-Testpress merged commit f0fad41 into main Mar 20, 2026
3 checks passed
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.

2 participants