Documenting code, one commit at a time.
The Reimpact/platform project is undergoing improvements to its testing infrastructure, specifically focusing on Filament resources. The goal is to ensure comprehensive test coverage for CRUD operations across various resources, while also addressing tenant-specific data handling.
Previously, testing Filament resources lacked sufficient coverage, especially
When building multi-tenant applications with Laravel, ensuring each tenant's database schema is correctly migrated can be a challenge. In the Reimpact platform, we encountered issues with tenant schemas either re-running all migrations on each deploy or skipping them entirely. This led to potential data inconsistencies and application instability.
Without a dedicated migration
When building multi-tenant applications with Laravel and Filament, it's crucial to ensure that operations are performed within the correct tenant context. This post addresses a common issue encountered when using Filament's massive upload feature where the tenant context was not active during Livewire form submissions, leading to data integrity violations.
Ensuring background jobs are correctly dispatched and optimizing resource allocation are critical for application stability and performance. This post explores recent enhancements to a Filament-based platform, focusing on ensuring consistent job dispatch across modules and improving worker allocation for resource-intensive tasks.
The Reimpact platform has undergone an update to align with Filament v5, specifically addressing changes in how actions are handled within tables. This adjustment ensures compatibility and leverages the latest features offered by the framework.
In previous versions of Filament, actions within tables were managed using Tables\Actions\Action.
Keeping dependencies up-to-date can be a headache, especially when upgrading major versions of frameworks. Let's look at how recent changes in the Reimpact platform addressed a namespace change in Filament v5 and improved tenant context resolution.
Filament is a popular Rapid Application Development (RAD) framework for Laravel.
The Reimpact platform is undergoing improvements to its multi-tenancy architecture, specifically focusing on tenant warehouse management. This involves refining database queries and updating tenant schemas for better isolation and data integrity.
Previously, the GeneratedReportResource was incorrectly querying the company_id on tenant-specific warehouse
In modern Laravel projects, choosing the right tools is crucial for efficient development and maintainability. The Reimpact/platform project is undergoing a transition from Nova to Filament, aiming to leverage Filament's capabilities for streamlined administration interfaces. This transition impacts testing strategies, requiring a shift from Nova-specific tests to those aligned with Filament.
When building multi-tenant applications with Laravel, ensuring proper tenant context and efficient file handling are critical. Recent updates to the Reimpact platform focus on improving these aspects, streamlining tenant schema management and simplifying large file uploads.
Proper tenant schema isolation is essential for maintaining data
Effective communication is crucial for any application. This post explores the new system email management features added to a Laravel project, focusing on centralizing email configurations and streamlining marketing workflows.
One key improvement is the creation of a centralized page for managing system emails. This provides a single point to
