Documenting code, one commit at a time.
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.
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.
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
Content Security Policy (CSP) is a crucial layer of defense against various types of attacks, including Cross-Site Scripting (XSS). However, sometimes certain routes or functionalities within an application require inline assets or scripts that are not compatible with strict CSP rules.
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
In single-page applications built with frameworks like Livewire, maintaining the correct user locale across all interactions can be tricky. The Breniapp project encountered an issue where the user interface language would revert to the browser's default (often English) during AJAX requests, even if the user had initially selected a different language.
En el proyecto landing, estamos mejorando la manera en que gestionamos las cookies de localización. Específicamente, hemos abordado un problema donde la cookie encriptada que guarda la localización del usuario podía fallar al desencriptarse entre diferentes despliegues o cuando Cloudflare interceptaba las redirecciones.
When building internationalized applications, handling user locales correctly is crucial. This post delves into how to validate and securely manage locale settings in PHP applications, focusing on preventing potential issues arising from stale or malformed locale data.
Encrypted cookies, particularly those storing locale information, can
