Documenting code, one commit at a time.
When developing with Laravel and Filament, encountering authentication issues can be a common challenge. Diagnosing these issues, especially vague 401 errors, requires a strategic approach to uncover the root cause. This post outlines a method for adding detailed logging to your authentication process to better understand and resolve such errors.
Have you ever experienced a dropdown menu staying open unexpectedly after resizing your browser? In Breniapp, a project focused on creating intuitive user interfaces, we encountered this exact problem with our admin dropdown. This post details how we tackled this UI persistence issue to ensure a smoother user experience.
When building dashboards for complex applications like Brenia, it's crucial to ensure that labels are crystal clear, especially when dealing with financial data. Ambiguity can lead to misinterpretations and incorrect assumptions, impacting user trust and decision-making.
In Brenia's consumption dashboard, the initial labels for cost columns, specifically
This post delves into recent improvements made to the onboarding process in Breniapp, focusing on a more intuitive and user-friendly experience. These changes align the onboarding flow with the Lovable specification, specifically targeting CTA selection and copy style options.
Previously, the process of selecting primary and secondary Call-to-Action (CTA) options during
In the Reimpact platform, we're always striving to optimize performance and ensure smooth operation. Recently, we encountered an interesting issue with the TopExceptionsWidget model that highlights the importance of correctly defining primary keys, especially when dealing with subqueries.
Filament, our admin panel framework, relies on $record->id to uniquely identify rows in
When developing widgets in Reimpact/platform, efficiency is key. A recent update addresses an issue with Filament's default sorting behavior in subqueries, specifically within the TopExceptionsWidget. Let's explore the problem and the solution.
Filament, a PHP framework, automatically applies ORDER BY model.id when using HasRecords. This default behavior becomes problematic
The Reimpact platform is undergoing continuous improvements to enhance its monitoring and reporting capabilities. Recent updates focus on refining how exceptions are tracked and how data is presented to users, ensuring a more informative and user-friendly experience.
One of the key updates involves resolving a compatibility issue within
The Reimpact/platform project is focused on [description]. Recent development efforts have concentrated on improving the way DPR (Data Protection Report) data is presented and managed within the platform. This involved transitioning from a static HTML table to a dynamic Filament TableWidget, offering enhanced features such as pagination, search, filtering, and translation support.
Working with large datasets in Filament can sometimes be overwhelming. Displaying all the information at once can make it difficult to quickly grasp key insights. This post explores how to enhance Filament tables by collapsing details by default and using translated filters for a more user-friendly experience, as recently implemented in the Reimpact/platform project.
When working with Filament, especially when displaying data from sources other than Eloquent models, you might encounter situations where the built-in features for filtering, searching, sorting, and pagination don't work out of the box. This post describes how to manually implement these features for array-based report tables within Filament admin panels.
