Skip to content

Drop the redundant public from the fixtures' set-only properties - #64

Merged
ahegyes merged 1 commit into
trunkfrom
style/protected-set-visibility
Oct 29, 2026
Merged

ahegyes merged 1 commit into
trunkfrom
style/protected-set-visibility

Conversation

@ahegyes

@ahegyes ahegyes commented Oct 29, 2026 •

Copy link
Copy Markdown
Owner

Summary. consumer-a, consumer-b and the core persona declare their kernel and migration runner as public protected(set), while a set-only visibility already reads as public. The packages write protected(set) alone, and the style rule covers plugin code too, so the fixtures that model a plugin's anatomy follow it. ahegyes/wordpress-plugin-template#19 makes the same change in the template.

  • Fixtures: consumer-a's $migrations and $kernel, consumer-b's $kernel and the core persona's $kernel drop the public; no behavior change.

Fixtures +4 −4 (3 files).

Testing.

  • composer quality-check passes: validate, changelog validation, PHPCS on both profiles, the PHPStan profiles and every fixture's, Unit 189 and Integration 1333.
  • composer test:integration:multisite passes (40, consumer-b's rows among them), and composer test:integration:php74 passes (2).

consumer-a, consumer-b and the core persona declared their kernel and
migration runner as public protected(set), while a set-only visibility
already reads as public. The packages write protected(set) alone, and
the style guide's rule covers plugin code, so the fixtures that model a
plugin's anatomy follow it as well.

Assisted-by: Claude Code:claude-opus-5-5
@ahegyes
ahegyes merged commit 900eb58 into trunk Oct 29, 2026
23 checks passed
@ahegyes
ahegyes deleted the style/protected-set-visibility branch October 29, 2026 11:11
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.

1 participant