feature/rating — Post-Order Rating

To collect post-order ratings and tips in a Flutter app, use a structured flow with a RatingPage featuring star input, tag chips, and a tip selector. It manages state with cubit and submits the rating entity via backend APIs.

Local persistence prevents duplicate rating prompts by marking orders as rated in local storage after submission. This ensures users are not repeatedly asked to rate drivers or restaurants for the same completed food delivery.

Yes, you can fetch dynamic rating tags by order type. The system retrieves specific RatingTagEntity lists for driver, food, or speed-related feedback, allowing users to select multiple relevant tags during the post-order rating submission.

The best way to implement a skip flow is by allowing users to dismiss the rating prompt with a one-time reminder. The UI supports skipping the rating process while still offering manual triggers from the order history later.

The tip selection UX handles tip selection visually within the rating interface but does not process the actual payment charge. It functions as a UI-only component that passes the tip amount to a separate charge flow.