test(v4): cover preflight and layer ordering

[colinaaa]

Summary

• Add Playwright test verifying preflight base styles (body, button, list) are applied via the virtual global CSS injected by the plugin.
• Add Playwright test verifying explicit @layer ordering () controls which declarations win across layers.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 significantly enhances the test suite for the rsbuild-plugin-tailwindcss-v4 by introducing new Playwright end-to-end tests. These additions ensure the plugin's core functionalities, specifically the application of preflight base styles and the correct resolution of CSS declarations based on @layer ordering, behave as expected within a browser environment.

Highlights

• Preflight Styles Verification: Added a Playwright test to confirm that Tailwind CSS preflight base styles (for body, button, and list elements) are correctly applied via the virtual global CSS injected by the plugin.
• CSS Layer Ordering Test: Added a Playwright test to verify that explicit @layer ordering correctly dictates which CSS declarations take precedence across different layers.

🧠 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.

Changelog

• test/basic/index.test.ts
  • Added a Playwright test to verify preflight base styles.
  • Added a Playwright test to verify CSS layer ordering.

Activity

• The PR description includes a comprehensive output of 28 Playwright tests passing successfully, demonstrating the current test suite's status and the successful execution of the new tests.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩

[gemini-code-assist]

Code Review

This pull request adds two new tests to cover preflight styles and CSS layer ordering. The tests are well-written and cover important functionality. My main feedback is to refactor the new tests to reduce code duplication by using Playwright's test.describe with beforeEach and afterEach hooks for setting up and tearing down the test server. This will improve the maintainability of the test suite.