Weave Code
Appointments For Laravel Laravel Package
roundly-consulting/appointments-for-laravel
Appointments for Laravel adds scheduling and booking to any Laravel app: define services, set availability, and manage appointments with an Eloquent-backed API. Includes migrations, models, and helpers to get booking flows running quickly.
Laravel package to manage appointments between entities.
Frequently asked questions about Appointments For Laravel
- How do I install appointments-for-laravel in a Laravel app?
- Install it with Composer using composer require roundly-consulting/appointments-for-laravel. The package is a standard Laravel package and should be auto-discovered through its service provider. Check the README for the exact config and migration publish tags, then run your migrations. Verify the install in a scratch branch before rolling it into production.
- Which Laravel and PHP versions does this package support?
- The provided release notes do not include a Laravel or PHP support matrix. Check the composer.json constraints in the repository and compare them with your current LTS baseline. If the constraints are unclear, run a quick install spike on your target Laravel version before committing to the package.
- What does the package include out of the box?
- It ships Eloquent models, factories, migrations, and helpers for scheduling and booking appointments. The package is designed around services, availability, and appointments between entities. That gives you a starting schema and API rather than a full UI. Review the migrations and model relationships to confirm they match your domain.
- How do I define services and availability?
- You define services and availability as Eloquent records using the models and migrations the package provides. The exact fields and relationships are documented in the README, so map your service catalog and availability rules onto those tables. Keep custom booking rules in your application layer unless the package explicitly supports them.
- Can I swap the package models for my own subclasses?
- Yes. The package exposes a configuration hook that lets a host application substitute its own subclass for the shipped model, which is useful for multi-tenant or white-label customization. Version 1.1.2 fixes the factories so they resolve the configured model instead of the concrete package class. Verify the swap across your own factory usage before relying on it.
- Do the package factories use my swapped model after 1.1.2?
- The 1.1.2 patch is specifically intended to make factories build the configured model. That matters if you swapped a model and previously got the package class back from factory()->create(). Confirm the fix for states, createMany, and relationship resolvers, not just the primary create path.
- How should I test booking flows with the shipped factories?
- Use the shipped factories to create services, availability, and appointments in tests, then assert against your configured model class. Add a targeted assertion that factory output is an instance of your subclass when you swap models. Also cover relationship factories and for()/has() resolution if your booking flow depends on them.
- What changed in version 1.1.2 and should I upgrade?
- It is a patch-level stabilization release with no migration, config change, or API break. The main change is that factories now resolve the configured model, closing a correctness gap in the model-swap contract. Upgrade via Composer and remove any local factory workarounds you added for the old behavior.
- What are the main risks when upgrading from an earlier version?
- The highest-probability disruption is the package's silent-failure history: tests that ran before 1.1.2 may have been green while asserting against the wrong model class. Schedule the upgrade and add regression coverage rather than discovering latent breakage in CI. Also verify whether config is resolved at call time or bound early, since that affects per-test overrides.
- What are alternatives to this package for appointment scheduling in Laravel?
- Alternatives include building a small Eloquent scheduling layer yourself or evaluating other Laravel booking packages with a broader feature set. This package is a good fit if you want a lightweight, Eloquent-centric starting point with model swapping. Compare schema fit, availability rules, test coverage, and maintenance activity before choosing.
Weaver
How can I help you explore Laravel packages today?