Documenting code, one commit at a time.
Recently, our team working on the Ryuu-no-Mi/Inmotech-Backend project addressed a critical security and usability issue related to Cross-Origin Resource Sharing (CORS) in our OAuth 2.0 implementation. This fix was crucial for ensuring seamless and secure interactions between our decoupled frontend applications and the authentication server, preventing common browser-based security blocks.
In the Ryuu-no-Mi/Inmotech-Backend project, we continuously strive to improve the user experience, particularly in property search and filtering. A key aspect of this is how we present geographical data to users, allowing them to quickly narrow down their search by location.
Previously, our property
Our ongoing work on the Inmotech-Backend project, a core component of Ryuu-no-Mi's property platform, recently focused on significantly improving its property search capabilities. With a catalog exceeding 30,000 properties, the challenge was to offer highly accurate geographical filtering and a responsive user experience through dynamic search facets.
Previously, our search
In the Ryuu-no-Mi Inmotech-Backend project, our goal is to provide a robust platform for property management. A critical component of any such platform is an intuitive and powerful search capability that allows users to find properties based on highly specific criteria.
Traditional basic search often falls short when users need to refine their results based on multiple criteria,
Searching for properties can often be a frustrating experience. Stiff search interfaces that don't dynamically adapt to your choices or provide relevant groupings can quickly turn a hopeful search into a chore. In the Ryuu-no-Mi/Inmotech-Backend project, we've recently rolled out a significant feature to transform this experience, particularly for 'venta' (sale) and 'alquiler' (rental)
Ever run into a seemingly simple database operation, like lowercasing a text field, only for it to throw a wrench in your application? This is a common pitfall when dealing with large text data types like CLOB (Character Large Object) in databases, especially within Java applications.
Imagine deploying a new environment or resetting development data, only to find critical fields consistently null or empty where they shouldn't be. This seemingly minor oversight can lead to cascading issues, from UI errors to incorrect business logic. Such was the challenge we recently addressed in our Ryuu-no-Mi/Inmotech-Backend project.
Our Ryuu-no-Mi/Inmotech-Backend handles a variety
Modern applications thrive on granular control, especially when it comes to searching and filtering data. For users interacting with platforms that manage diverse information, the ability to pinpoint specific items based on their attributes is crucial. This post delves into a recent enhancement made to our backend application, focusing on improving its search capabilities by
Working with stale or insufficient test data can significantly hinder development and compromise the reliability of testing. Developers often find themselves wrestling with limited datasets that don't reflect real-world scenarios, leading to missed edge cases and a less robust application.
At Ryuu-no-Mi's Inmotech-Backend project, we faced similar challenges.
Imagine a gym membership system where every family member needs their own access, but the family's main plan dictates how many members can join and when their access expires. This challenge is similar to what we tackled in Inmotech-Backend, enhancing our subscription management to support more flexible agency and agent-level plans.
Previously, our
