- Is siganushka/api-factory-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle that registers API factory services through Symfony's DependencyInjection container. It is not described as a native Laravel package. Laravel teams can evaluate it for Symfony component compatibility, but should not assume Laravel service-provider or auth-guard behavior out of the box.
- How do I install and register siganushka/api-factory-bundle in a Symfony application?
- Install it with Composer and enable the bundle using the normal Symfony bundle registration process. Then define and configure the factory services you need through the container. Because the package is lightweight and extensible, start with the README's bundle setup and configuration examples before building reusable application-wide workflows.
- Can I use siganushka/api-factory-bundle in a Laravel application?
- The assessment says it is feasible for Laravel apps on PHP 8.2+ with compatible Symfony component versions, but it is not a native Laravel integration. Expect to bridge Symfony DependencyInjection and Security configuration into Laravel's container or auth model, or use only the package's lower-level services. Laravel 10 or earlier should be treated as high risk until a compatibility matrix confirms support.
- Which PHP and Symfony versions are required for siganushka/api-factory-bundle v1.2.0?
- The provided assessment identifies PHP 8.2 and Symfony 7.4 minimums as the primary breaking dependency change. Those requirements can conflict with older Laravel applications or apps pinned below PHP 8.2. Audit PHP, Laravel, and Symfony component constraints before adopting v1.2.0.
- Does the bundle provide native Laravel auth guards for GitHub or WeChat?
- No. The assessment describes Symfony Security firewalls for GitHub and WeChat, not native Laravel auth-guard replacements. Laravel teams should plan an adapter layer or use only lower-level services. Validate login, callback, and user-provisioning flows in staging before production.
- How do I configure reusable API factories with the Symfony service container?
- Register factory services through Symfony's DependencyInjection container and define the configurable factory settings your application needs. The bundle's purpose is to let you configure and reuse factories with minimal boilerplate. For maintainability, use the resolver tag constants where applicable and verify compiler pass behavior after changes.
- What is UserPersisterInterface and when do I need to implement it?
- UserPersisterInterface is described as an extensibility point for custom user persistence. The provided context does not confirm a default binding, so verify the package defaults before relying on them. Implement or bind it when your application needs custom persistence wiring, and review the implementation against package expectations.
- Are the GitHub and WeChat firewalls production-ready?
- GitHub support has lower operational overhead but still requires OAuth app configuration and secrets. WeChat adds regional and provider-specific needs, including credentials, callback domains, and possible differences across MP, Open, and MiniApp flows. The assessment does not confirm production readiness across every WeChat flow, so test each required flow in staging before rollout.
- Are old string-based resolver tags still supported in v1.2.0?
- The resolver tag constants are low risk and improve maintainability, but backward compatibility with old string-based tags must be verified. The assessment says existing resolver configuration should remain compatible if old strings are still accepted. Audit the compiler pass behavior and replace strings with RESOLVER_TAG or RESOLVER_EXTENSION_TAG only after testing.
- What is the rollback path if Symfony 7.4 conflicts with my Laravel app?
- Pin the previous package version and dependency constraints before upgrading, then test v1.2.0 in staging. Roll out progressively with feature flags so you can revert to the prior package version if Symfony 7.4 conflicts with the host application. First confirm the supported Laravel, PHP, and Symfony compatibility matrix to avoid dependency drift.