Weave Code
Core Laravel Package
beloop/core
Core component of the Beloop LMS suite: shared foundations used by other Beloop components and bundles built on Symfony. MIT licensed. Read-only split package—use the main beloop/components repository for issues, questions, and PRs.
[READ-ONLY] Subtree split of Beloop Core component
Frequently asked questions about Core
- Can I use Beloop Core directly in Laravel 9/10 without PHP 8.0+ polyfills?
- No, Beloop Core requires PHP 7.2+, but Laravel 9+ mandates PHP 8.0+. You’ll need to either enforce PHP 8.0+ in your project via `composer.json` platform config or create a compatibility layer for PHP 8.x features like named arguments and union types. Test thoroughly—some legacy code may break silently.
- Does Beloop Core support Laravel’s service container or do I need to manually register services?
- Beloop Core does not natively integrate with Laravel’s service container. You’ll need to create a custom service provider to bind Beloop’s dependencies manually. This adds complexity, especially if the package relies on Symfony’s DI system. Plan for a wrapper class to bridge the gap between Symfony and Laravel’s container.
- Will Beloop Core’s database migrations work with Laravel’s Schema builder in Laravel 9+?
- Likely not out of the box. Laravel 9+ introduced changes like named arguments in query builders (e.g., `where('active', '=', 1)`), which may conflict with Beloop Core’s older syntax. Audit migrations for deprecated methods and rewrite them using Laravel’s Schema builder or create an adapter layer.
- Are there any known conflicts with Laravel’s first-party packages like Sanctum or Horizon?
- Yes, Beloop Core was built for Symfony and lacks native integration with Laravel’s auth systems (e.g., Sanctum, Passport). If the package includes custom guards or auth logic, you’ll need to build a translation layer or replace its auth components entirely. Test early with your chosen Laravel auth stack.
- How do I handle events or listeners from Beloop Core in Laravel?
- Beloop Core doesn’t use Laravel’s event system, so you’ll need to manually dispatch events or create a proxy layer. For example, wrap Beloop’s event triggers in Laravel’s `Event::dispatch()` calls. Alternatively, use Laravel’s listeners to react to Beloop’s internal events via custom logic.
- Is Beloop Core actively maintained, or should I expect breaking changes?
- This package is **read-only**, meaning no new features or fixes will be added here. All development happens in the [beloop/components](https://github.com/beloop/components) repo. The PHP 7.2+ requirement suggests minimal updates, but Laravel 9+/10+ may expose hidden issues. Treat it as a legacy dependency with high integration risk.
- Can I use Beloop Core for business logic only, or does it include infrastructure code (e.g., database, HTTP)?
- The package’s purpose isn’t clearly documented, but as part of an LMS suite, it likely includes both business logic (e.g., course management) and infrastructure (e.g., database models, API clients). If it’s tightly coupled to Symfony’s HTTP layer or Doctrine ORM, you’ll need to abstract those parts for Laravel compatibility.
- What’s the best way to test Beloop Core in a Laravel project before full integration?
- Start by isolating Beloop Core in a separate service or microservice using Laravel’s HTTP clients or queues to communicate. Mock its dependencies and test critical paths (e.g., authentication, data flows) in a controlled environment. Use PHPUnit to verify interactions with Laravel’s components like Eloquent or caching.
- Are there alternatives to Beloop Core for LMS functionality in Laravel?
- Yes, consider Laravel-specific packages like **AsgardCMS**, **Filament**, or **Laravel Nova** for LMS-like features. For open-source alternatives, **Moodle’s Laravel wrappers** or **Open edX integrations** might fit better. If you’re committed to Beloop, evaluate the effort vs. rewriting logic in native Laravel components.
- How do I handle dependency conflicts between Beloop Core and Laravel’s illuminate/* packages?
- Use `composer why-not` to detect conflicts, then pin compatible versions in your `composer.json`. For example, if Beloop Core depends on `symfony/console:v4.0`, override it with `composer config extra.adapt-phar-versions true` or create a custom alias. Expect manual resolution for packages like `monolog` or `psr/log` where versions diverge.
Weaver
How can I help you explore Laravel packages today?