Avinash Rajesh
20475ace73
- Refactored processBookingCancellation to simplify parameters and remove redundant notification arguments. - Added util::UserType parameter to differentiate cancellation flows for CUSTOMER vs TECHNICIAN. - Updated cancelCustomerServiceBookings to use processBookingCancellation with util::UserType::CUSTOMER. - Updated cancelTechnicianJobs to use processBookingCancellation with util::UserType::TECHNICIAN. - Enhanced booking status handling by including IN_PROGRESS status in cancellation checks. - Ensured job cards are consistently marked CANCELLED and inventory restored. - Fixed duplicate notification issue where customers received multiple alerts when technician was removed. Fixes #1807
Introduction
TODO: Give a short introduction of your project. Let this section explain the objectives or the motivation behind this project.
Getting Started
TODO: Guide users through getting your code up and running on their own system. In this section you can talk about:
- Installation process
- Software dependencies
- Latest releases
- API references
Build and Test
TODO: Describe and show how to build your code and run the tests.
Contribute
TODO: Explain how other users and developers can contribute to make your code better.
If you want to learn more about creating good readme files then refer the following guidelines. You can also seek inspiration from the below readme files: