Skip to content

style: Changed code style to fix lint-pipeline. #175

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.

Sign up for GitHub

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

Jump to bottom
Open
FloWinge wants to merge 1 commit into
base: main
Choose a base branch
from
Open

style: Changed code style to fix lint-pipeline. #175

FloWinge wants to merge 1 commit into from

Conversation

@FloWinge
Copy link
Contributor

@FloWinge FloWinge commented Dec 12, 2025 •
edited by coderabbitai bot
Loading

Hey @tobimori! Just saw, that my last pr caused an pipeline error after merge. This should fix it ;-)

Summary by CodeRabbit

  • Style
    • Improved whitespace formatting in PHP closure declarations.

✏️ Tip: You can customize this high-level summary in your review settings.

@dosubot dosubot bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Dec 12, 2025
@coderabbitai
Copy link

coderabbitai bot commented Dec 12, 2025 •
edited
Loading

Walkthrough

Whitespace formatting updates to three PHP arrow function declarations in the config file. Parameter spacing standardized by adding a space between fn and parentheses (e.g., fn() to fn ()). No functional or logic changes.

Changes

Cohort / File(s) Summary
PHP Arrow Function Formatting
config/site-methods.php		 Standardized spacing in three closure declarations: schema, schemas, and lang. Updated arrow function syntax from fn(...) to fn (...) for consistency.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

No functional changes; purely stylistic whitespace adjustments to match code style conventions.

Poem

🐰 A space here, a space there,
Formatting with care!
Arrow functions stand so tall,
With proper spacing for us all. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: a code style adjustment to fix lint-pipeline issues. It relates directly to the whitespace/formatting changes in the PHP file.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 74f822a and 9c4e7dc.

📒 Files selected for processing (1)
  • config/site-methods.php (1 hunks)
🧰 Additional context used
🧬 Code graph analysis (1)
config/site-methods.php (3)
classes/Seo.php (2)
  • Seo (7-29)
  • option (20-28)
classes/SchemaSingleton.php (2)
  • getInstance (16-27)
  • getInstances (29-36)
classes/Meta.php (1)
  • normalizeLocale (50-60)
🔇 Additional comments (1)
config/site-methods.php (1)

8-10: Consistently applied formatting fix for arrow function declarations.

The changes correctly add spacing between the fn keyword and the opening parenthesis, which aligns with PSR-12 and standard PHP coding conventions. All three arrow functions in the file have been updated consistently. A spot check across the codebase confirms all other arrow functions already follow this formatting standard.

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@FloWinge