Repository navigation
Improve ticket tier selection and pricing - #168
Conversation
Users should see capacity and price info before confirming, even when there is only one ticket tier available.
Add integer price_amount column to eventTiers for structured numeric pricing (KRW). Prepares for payment integration.
Add formatPrice utility for KRW formatting (15000 → ₩15,000). Update tier APIs, dashboard form, and registration page to use numeric priceAmount with fallback to the existing price label.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (12)
📝 WalkthroughWalkthroughThe changes introduce numeric price storage to event tiers via a new Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
priceAmountinteger column) to event tiers for KRW formatting (15000 → ₩15,000) and future payment integrationformatPrice()with fallback to the existingpricelabelTest plan
Summary by CodeRabbit
New Features
Improvements