Symfony Common Helpers Laravel Package

Getting Started

• Install only if you already use Symfony components inside your Laravel app (e.g., via a bridge or a legacy module): composer require pixiekat/symfony-common-helpers.
• First place to look: the GrantVoterTrait (or similarly named trait) — release 2.0.3 added new methods there. Inspect the trait source to see the exact helper signatures.
• First use case: simplify a custom Symfony voter that you invoke from Laravel. Apply the trait to your voter class, then use the new helper methods to grant/deny votes instead of manually returning VoterInterface::ACCESS_GRANTED / ACCESS_DENIED with repeated conditionals.
• If you are not using Symfony’s Security component, this package has little day-to-day value for a typical Laravel codebase — Laravel’s Gate/Policy system is the native alternative.

Implementation Patterns

• Trait-based voter helpers: In a custom voter class, use GrantVoterTrait; and replace hand-written grant/deny logic with the new methods added in 2.0.3. Typical workflow: implement supports() and voteOnAttribute(), then call the trait’s helpers for common grant conditions (e.g., role checks, attribute matching).
• Bridging to Laravel Gate: If you need to reuse Symfony voters from Laravel, create a small adapter that resolves the voter and calls vote(). Register it as a custom Gate closure or a policy method. The trait reduces the boilerplate inside the voter, not the bridge.
• Mixed Symfony/Laravel module: Use the package in a submodule that already depends on symfony/security-core. Keep the trait usage isolated to that module so Laravel-native code stays on Gate/Policy.
• Composition over inheritance: If your voter already extends a base class or uses another trait with conflicting method names, wrap the trait’s logic in a small helper class instead of using the trait directly.
• Upgrade path from 2.0.2: 2.0.3 is a patch release with code cleanup and new trait methods. No breaking changes are indicated. Run your test suite after upgrading, especially if you extend or override the trait.

Gotchas and Tips

• Not a Laravel package: There is no service provider, facade, config file, or auto-discovery. You must manually wire anything you use.
• Symfony version coupling: The trait depends on Symfony’s Security component interfaces. Check composer show symfony/security-core and ensure compatibility with your Laravel/Symfony bridge versions.
• Trait method conflicts: PHP will fatal if your class already defines a method with the same name as a new trait method. After upgrading to 2.0.3, run php -l or your test suite to catch collisions early.
• Debugging new trait methods: Use ReflectionClass::getTraitNames() and getTraitAliases() or your IDE’s trait method listing to see what 2.0.3 added. The release notes do not name the methods, so inspect the diff or the trait source.
• Code cleanup risk: “Code cleanup” in a patch release can occasionally change internal behavior (e.g., visibility, default return values). If you relied on undocumented behavior, add a regression test around your voter’s decisions.
• Extension points: You can override trait methods in the using class, alias them (GrantVoterTrait::method as protected), or extract the logic into a dedicated service if you need multiple voters to share it without trait coupling.
• Laravel-native alternative: For most Laravel apps, prefer Gate/Policy. Use this package only when you are deliberately sharing voter logic with a Symfony-based component or migrating legacy code.