Documenting code, one commit at a time.
Building robust fleet management tools requires a balance between data density and user experience. In the Ryuu-no-Mi project, we recently focused on improving the interaction layer by refining our detail views and company management interfaces.
When managing complex datasets—like vehicle fleets—the primary challenge is avoiding 'information overload.
Complexity in UI components often creeps in silently. When a table component and its associated form start growing, it becomes difficult to maintain state and layout. In our work on the Ryuu-no-Mi/Gestion-de-flotas project, we recently focused on decoupling these concerns to improve developer experience and component stability.
Initially, our dashboard
Managing fleet operations requires a balance between accessibility and security. In our recent work on the Ryuu-no-Mi/Gestion-de-flotas project, we focused on refining the dashboard access layer and formalizing our authentication state management to ensure a smoother, more secure user experience.
Previously, managing user sessions in our
At Ryuu-no-Mi, we have been focusing on the Gestion-de-flotas project to refine our administrative dashboards. As our vehicle inventory grows, managing data effectively requires more than just displaying lists; it requires precise control and safe interaction patterns.
Initially, our dashboard was a simple read-only list.
At Ryuu-no-Mi, the Gestion-de-flotas project focuses on modernizing our fleet management ecosystem. A critical component of this effort is ensuring secure and reliable access for our team. We recently completed a significant update to our authentication flow, transitioning to a robust token-based system to handle user sessions more effectively across our Vue.js-based frontend.
Authentication is the gateway to any application. If the front door is broken, the entire experience falls apart before it even begins. I have been working on the Ryuu-no-Mi/visitALO_Front project, where the primary objective was to establish a solid foundation for user access through clean, scalable components.
When implementing login and registration,
On the Inmotech Frontend project, we recently tackled a common challenge in API communication: inconsistent URL query parameter serialization. This often arises when integrating with backend services that expect a specific format for array parameters, differing from the default behavior of popular HTTP clients like Axios.
Ever found yourself debugging an API request only to realize the backend
