Documenting code, one commit at a time.
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
When developing multi-tenant applications using Laravel, maintaining schema consistency across tenants is crucial. A recent fix in the Reimpact platform addressed an issue where the products table in tenant schemas was missing specific columns, leading to job failures.
The RefreshRecipeWeights job was failing because the recipe_weight and
In the Reimpact/platform project, we're constantly striving for a cleaner, more maintainable codebase. Recently, we undertook a refactoring effort focused on removing unnecessary relationships, improving widget functionality, and ensuring data consistency across tenants.
One area identified for improvement was the MassiveUploadWithErrorsResource.
When working with UI frameworks like Filament in Laravel projects, you sometimes encounter situations where the framework's CSS pipeline interferes with custom styling. We recently ran into this issue in the Reimpact platform while developing the QuickLinksWidget.
Filament, being based on Tailwind CSS, compiles its own version of Tailwind. This can lead to inconsistencies if your project's
When developing multi-tenant applications using Laravel, managing database schemas can become complex. Each tenant might require specific customizations, including additional columns in existing tables. This post addresses how to handle such scenarios by focusing on adding a homologation_level column to a products table within a tenant-specific schema in the Reimpact platform.
The Breniapp/brenia project focuses on streamlining the user onboarding experience. Recent efforts have centered on refining visual reference handling, simplifying steps, and improving the overall user interface.
The previous onboarding flow had several areas needing improvement:
User experience is key to successful onboarding. Small tweaks can have a big impact on how new users perceive and interact with an application. Recent work on Breniapp focused precisely on these kinds of improvements.
Several adjustments targeted specific pain points in the onboarding flow:
The Breniapp project focuses on providing a streamlined experience for its users. Recent efforts have been directed towards improving the user experience during the onboarding process, specifically addressing issues related to file uploads and overall workflow.
Recent work has concentrated on fixing user experience issues that arise during the file upload steps of the
