Api Factory Bundle Laravel Package

Product Decisions This Supports

• Authentication roadmap / feature expansion: v1.2.0 adds GitHub and WeChat security firewalls (wechat_mp, wechat_open, wechat_miniapp). This directly supports decisions to add social login and, critically, to enter China-facing markets where WeChat login is often a launch requirement rather than a nice-to-have.
• Build vs. buy: The new UserPersisterInterface makes user persistence pluggable. Teams can keep their existing user tables, domain model, and lifecycle logic instead of adopting the package’s storage assumptions. That lowers the “buy” risk and makes adoption viable for products with established identity models.
• Platform modernization: The PHP 8.2 / Symfony 7.4 minimum is effectively a platform-floor decision. It can be used as a forcing function to standardize on a modern runtime, but it will block legacy applications until upgraded.
• Extensibility without forking: New RESOLVER_TAG and RESOLVER_EXTENSION_TAG constants in ResolverConfiguratorPass reduce the need for custom compiler passes or maintained forks when teams need custom resolver behavior—useful for multi-tenant, white-label, or region-specific auth flows.
• Use cases: B2C social login, marketplace seller onboarding via GitHub, WeChat Mini Program authentication for China market entry, and consolidating multiple social providers behind one integration layer.

When to Consider This Package

• Consider it when: you need GitHub and/or WeChat OAuth/social login; you are on PHP 8.2+ and Symfony 7.4+ (or a Laravel version shipping compatible Symfony components); you want to retain your own user model via UserPersisterInterface; or you need DI-level resolver customization without maintaining a fork.
• Strong fit: products expanding into China that need WeChat MP/Open/MiniApp login, teams standardizing authentication on a configurable firewall-based approach, and organizations that want to avoid building and maintaining provider-specific OAuth code.
• Look elsewhere when: you are on PHP <8.2 or Symfony <7.4 and the upgrade cost outweighs the benefit; you only need simple email/password authentication; Laravel Socialite or first-party framework guards are sufficient; you do not need WeChat/GitHub and want a smaller dependency footprint; or you require vendor-backed SLAs and the package’s maintenance/community signals are insufficient.
• Framework-fit caveat: the Symfony 7.4 floor may outpace the Symfony components bundled with the Laravel version you run. Validate compatibility before committing it to a Laravel roadmap.

How to Pitch It (Stakeholders)

• Executive summary: v1.2.0 turns social authentication into a configurable capability rather than a custom build. The WeChat firewalls unlock China market entry without a separate auth stack; UserPersisterInterface lets us keep our existing user system; and the new resolver tags reduce long-term fork risk. The trade-off is a platform-floor bump to PHP 8.2 / Symfony 7.4, which should be treated as a breaking upgrade for older applications.
• Recommendation: run a short spike if GitHub or WeChat login is on the roadmap, especially for China-facing products. Otherwise defer until the runtime upgrade is already planned. Treat v1.2.0 as the minimum version for new work and avoid backporting to older runtimes.
• Engineering note: the release is versioned as a minor but includes a de facto breaking platform-floor change. Audit PHP/Symfony versions first; validate firewall integration against existing security configuration; test WeChat flows in sandbox accounts; and confirm that UserPersisterInterface matches the current user lifecycle before adoption.