Ever had a loading indicator that flashes annoyingly, appearing and disappearing seemingly at random? We did, in the Reimpact/platform project. A previously implemented wire:loading approach for our charts was causing more frustration than help.

The Problem

The original implementation relied on wire:loading which, while convenient, proved unreliable for complex interactions.

The Reimpact platform focuses on delivering streamlined and efficient solutions. Recently, we've been focusing on improving code maintainability and reducing potential runtime errors. One key area has been ensuring code adheres to strict typing.

The Improvement

A recent update focused on adding a type hint to the enforceSingleSession parameter. This seemingly small change has a significant

Working on the Reimpact platform often involves juggling multiple moving pieces. Recently, we encountered a peculiar issue: the lingering presence of duplicate migration files.

The Phantom Menace

Our deployment process began failing intermittently. After some digging, we discovered the root cause: duplicate migration files for key components like warehouses, brands, and massive uploads.

When working on the Reimpact platform, a key aspect is ensuring data accuracy and efficiency. Recently, we addressed an issue within the generated reports functionality. The goal was to streamline data processing and eliminate redundant calculations, resulting in a more efficient system.

Identifying the Issue

The initial analysis revealed that certain data points within the generated reports

When managing multi-tenant applications, ensuring data integrity across all tenants is crucial. Recently, while working on the Reimpact/platform, we encountered an issue during tenant migrations related to non-nullable columns. Here’s how we addressed it.

The Problem

In a multi-tenant architecture, each tenant often has its own database schema. During migrations, these schemas need to be

Introduction

When building multi-tenant applications, choosing the right architecture is critical. This post explores how to leverage PostgreSQL schemas within a Laravel application to achieve tenant isolation, enhance security, and improve scalability.

The Multi-Tenant Challenge

Traditional multi-tenant approaches often involve sharing a single database and distinguishing tenants by a

Introduction

The Reimpact platform recently underwent a navigation update to improve user experience within the Filament admin panel. This update focused on ensuring consistent and correct redirection after login and impersonation actions.

The Problem

Previously, users logging in or utilizing the impersonate feature were being redirected to outdated Nova paths, specifically

The Reimpact platform is undergoing a transition of its module URLs from Nova to Filament. This post details how we fixed a login redirect issue that arose during this migration.

The Problem

After migrating the Packaging module to Filament, users were experiencing redirect issues upon login when the MODULE_SELECTOR_SYSTEM feature flag was enabled.

The Problem

In the Reimpact platform, we encountered an issue where session validation middleware was causing unexpected logouts during user impersonation. Specifically, the CheckValidSession and EnsureSingleSession middlewares were interfering with the impersonation process, leading to a frustrating user experience.

The Cause

The root cause of the problem lies in how the session is

Introduction

When developing dashboards that rely on precise data comparisons in PostgreSQL, case sensitivity can be a silent but critical issue. This post examines a case in the Reimpact platform where case sensitivity in unit comparisons caused dashboard calculations to return incorrect results, and how it was resolved.

The Problem: Case-Sensitive Comparisons

PostgreSQL, by default,