Apply fixes from StyleCI

[rennokki]

This pull request applies code style fixes from an analysis carried out by StyleCI.

---

For more information, click here.

[gemini-code-assist]

Summary of Changes

Hello @rennokki, 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 primarily focuses on applying automated code style fixes identified by StyleCI. The changes include minor formatting adjustments to improve code consistency and a correction to a type hint in a test file, ensuring better adherence to modern PHP standards.

Highlights

• Code Style Formatting: Adjusted break statements in switch cases within src/KubernetesCluster.php to be on a new line, improving code readability and adhering to style guidelines.
• Type Hint Correction: Updated the test_from_environment_variable method in tests/ConfigurationTest.php to correctly use a nullable string type hint (?string) for the $context parameter.

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

[Copilot]

Pull request overview

This pull request applies automated code style fixes from StyleCI to ensure the codebase adheres to PHP coding standards. The changes include proper nullable type hints and standardized switch statement formatting.

Changes:

• Updated nullable type hint syntax in test method parameter
• Reformatted switch statement breaks to follow PSR standards

Reviewed changes

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

File	Description
tests/ConfigurationTest.php	Added proper nullable type hint (?string) to test method parameter
src/KubernetesCluster.php	Reformatted switch statement to place break statements on separate lines per PSR standards

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gemini-code-assist]

Code Review

This pull request applies style fixes from StyleCI. The change in tests/ConfigurationTest.php to use nullable types is a good improvement. However, the formatting of the switch statement in src/KubernetesCluster.php is unconventional and not fully compliant with PSR-12. I've suggested a cleaner formatting for better readability and adherence to coding standards.

[gemini-code-assist]

While breaking the case statements into multiple lines is a step towards better readability, the current formatting is unconventional and doesn't fully align with PSR-12 coding standards. For better readability and consistency, the statement within each case should be on its own line and indented, as recommended by PSR-12.

            case 'kubeconfig':
                $this->configureWithKubeConfigFile($config);
                break;
            case 'http':
                $this->configureWithHttpAuth($config);
                break;
            case 'token':
                $this->configureWithToken($config);
                break;
            case 'cluster':
                $this->configureInCluster($config);
                break;
            case 'variable':
                $this->configureWithKubeConfigVariable($config);
                break;

References

1. According to PSR-12, the body of each case should be on a new line and indented for better readability. The break keyword should be at the same indentation level as the case body. ^(link)