Fix Billing Details Population Bug

@raj3292

With over a decade of experience in web development, primarily with PHP, I can assure you that I am skilled and attuned to the Spring and Project Reactor frameworks. Your project needs a fix that not only addresses the bug but also preserves the non-blocking flow of your codebase. This matches my capability as well as my commitment to delivering top-quality products that consistently meet and exceed clients' needs. My proficiency extends beyond programming alone; I've worked in diverse setups from small startups to Fortune clients. As a result, I possess excellent teamwork skills enriched by experiences in cooperation and communication, which aligns tightly with your desire for consistency in your codebase implementation. Moreover, my familiarity with crucial tools like Github, SourceTree, Asana, and Trello makes it easier for me to fit into your established operations seamlessly. Efficiency will not be compromised. Trusting me with this task guarantees a successful project completion where unit tests fulfill all desired conditions and green builds persist. Chargers will no longer suffer from wrong invoices!

@nileshpvw

I’d be happy to work on your project. I have 12+ years of experience in developing customized software tools, web applications, and desktop solutions for both internal teams and external clients. My skills include C, C++, C#, ASP.NET (WinForms & MVC), .NET Core, WPF, Flutter, and database work with MS SQL & MySQL. I’ve also built and integrated RESTful APIs and modern web interfaces using HTML, CSS, Bootstrap, JavaScript, and jQuery. Once you share a few more details about your project or the tool you want developed, I can suggest the best approach, timeline, and a technical plan tailored to your needs. Let’s connect and discuss your requirements further.

@ravisuneelsingh

Hi, I’ve carefully read the issue and I understand exactly where the bug is coming from. Right now, account type and account number are being treated independently, which allows cross-mixing across profiles in a reactive flow — that’s a serious billing risk. How I’ll fix it (clean & consistent with your codebase): Treat accountType + accountNumber as a single atomic pair Follow the existing overwrite/append pattern already used for other fields Logic: Overwrite → if either field is present in preferences, replace both together Append → keep existing values unless the preference contains a complete pair Ensure no blocking calls (pure Mono / Flux / flatMap, no side effects) Refactor into a small helper if needed to keep the service readable and testable What I’ll deliver: Updated service class with correct reactive flow Any helper method/class touched, kept minimal Unit tests covering: overwrite replaces both fields together append preserves both unless full pair exists no cross-mixing under any null / non-null combination I’ll run the logic through edge cases before delivery so your pipeline stays green on first run. Quick check: are you using JUnit 5 + StepVerifier, or is there an internal testing utility already preferred in the repo? Best, Ravi S. Backend Developer | Java • Spring • Reactive Systems

@ruthranvicky4

I am currently working as java developer and having 3+ years experiences. I have worked in accounts related projects and logistic projects it is easy to complete the bug and will submit the robust code to you on the given time.

@garronwallace

I’m confident I’m the right person for this project. You need a modern, smooth, and intuitive fix in your reactive Spring backend to keep account type and number inseparable and handle overwrite/append logic consistently, preserving a non-blocking flow. I bring deep experience with Spring Reactor, reactive programming, and writing clean, optimized, automated unit tests. I’m new to Freelancer, but I have strong real-world experience and have completed many successful projects outside the platform. Let’s talk through your goals — I’d love to help bring this to life. Regards, Garron Levi Wallace

@SashaDev1

Hello, Having worked extensively in API and Backend Development over the years, I believe my expertise aligns perfectly with your project needs. Your bug description is detailed and specific, requiring a deep understanding of reactive programming and Spring framework, which I possess. My skill set includes extensive experience in Project Reactor, Mono, Flux, flatMap, etc., all of which are essential for your task. Furthermore, my strong background in Full-Stack development has allowed me to develop a keen eye for detail and fix critical issues with precision while ensuring that the bigger picture is never compromised. This is evidenced by my ability to create code that maintains a consistent pattern throughout, as required by your project. Lastly, I understand the value of thorough testing and continuous integration in ensuring software quality. Therefore, I assure you of creating not just a solution that addresses your issue but also comprehensive unit tests to prove its correctness. I look forward to having the opportunity of working on this project and delivering the level of quality that lives up to your expectations. Thanks!

@saip096

Hi, I can fix this issue cleanly while preserving the reactive (Mono/Flux) flow. I understand the problem: account type and account number must be treated as a single inseparable pair, and the overwrite/append behavior should follow the existing pattern used in the codebase to avoid any cross-mixing. Approach: - Encapsulate account type + number as a single logical unit - Apply overwrite only when preference indicates overwrite - Apply append only when a full pair is present - Ensure no blocking calls and keep flatMap chain intact - Add unit tests covering all null/non-null combinations I’ve fixed similar Spring Boot logic bugs and production data consistency issues before. I can start immediately and deliver with tests. Thanks