- How do I install d4ve-r/livewire-resource-time-grid in a Laravel app?
- Install it with Composer using the package name d4ve-r/livewire-resource-time-grid, then publish the package views and config as described in the repository. After publishing, drop the Livewire component into any Blade view and bind a resource collection plus your event or slot data. Because the release is v0.0.1, pin the exact version in composer.json rather than using a caret range.
- Does livewire-resource-time-grid support Livewire 2 or only Livewire 3?
- The v0.0.1 changelog consists of a single line stating that Livewire 3 support was added, so Livewire 3 is the supported target. Applications still on Livewire 2 are effectively excluded. If Livewire ships a future major version, expect to wait for the sole maintainer to update the component before you can upgrade.
- Is it safe to require ^0.0.1 for this package?
- No. SemVer treats 0.0.x as unstable, meaning any patch bump may contain breaking changes, so a caret range invites unattended breakage. Pin the exact string 0.0.1 in composer.json and commit your lockfile. Treat every version bump as a reviewed change with a changelog diff, not an automatic Dependabot merge.
- How do I render events across multiple resources in a time grid with Livewire?
- The component renders resources on one axis and time slots on the other, so you pass it a resource collection and an event or slot model that maps bookings into the grid. The package handles the presentation only; defining how your bookings map to slots and what a slot click does server-side is your responsibility. Confirm whether the slot model is opinionated about Eloquent contracts and column names before building your adapter.
- How are timezones and daylight saving time handled in this time grid?
- Timezone and DST behavior is not documented in the release, so you must verify it from the source before relying on it. The key question is whether slot generation happens server-side in UTC with conversion at render time, or purely client-side. If the grid is a core screen for scheduling across regions, plan an explicit spike for DST transitions and user timezone conversion.
- Does the package support drag and drop, and how do I persist event moves?
- The package is a presentation-layer component; any drag, drop, or slot-click interaction must be wired to your own Livewire actions and persistence logic. There is no documented persistence loop in v0.0.1, so you define where authorization runs and how conflicting bookings are rejected. Read the component source to see which browser events it emits before assuming a specific interaction contract.
- What PHP and Laravel versions does livewire-resource-time-grid require?
- Check the require and require-dev blocks in the package's composer.json and compare them against your own PHP, Laravel, and Livewire matrix. The release notes do not publish a formal compatibility matrix or deprecation policy. Also confirm that the package does not transitively pin Livewire in a way that blocks your own Livewire patch upgrades.
- Can I publish and override the grid views without forking the package?
- The integration steps include publishing views and config, which normally means you can override Blade templates inside your own resources directory. That lets you patch markup, styling, and accessibility tweaks without maintaining a fork. Verify this holds for the specific templates you need to change, since there is little documentation at v0.0.1 and the source is the reference.
- Is livewire-resource-time-grid production ready and actively maintained?
- Treat it as a pre-alpha artifact: v0.0.1 is the first tag, the changelog is one line, and it is a single-author repository with no visible release cadence, security policy, or LTS branch. It is reasonable for a secondary scheduling screen in a Livewire-centric Laravel app where the team is comfortable reading vendor source. Avoid it where the grid is the product's core surface or where you need SLA-backed maintenance.
- What are alternatives to livewire-resource-time-grid for Laravel scheduling UIs?
- Common routes are FullCalendar or similar JavaScript schedulers wrapped in a Livewire component, or a custom Blade and Alpine grid backed by your own slot generation service. Each alternative shifts the hard problems, such as DST handling, overlap layout, and accessibility, into your codebase rather than removing them. Choose based on whether you want Livewire-owned state or a JavaScript calendar library owning the render layer.