* perf: Refactor bookings queries for API
* fix syntax
* fixing vars
* Inverted the filter by attendees if
* fixed prisma filter issue
* Defaulting list of emails to empty array
* Only running 2 queries if we have data to filter by
* Reverted changes that have been separated out to other PR
* fix: ts build error
* adds tests + extracts logic for units
* fix integration tests
* fix tests expectes
* Fix test
* switching back
* attempt : fix tests
* test: add test for duplicate bookings (#21165)
* feat: Add tests for booking and duration limits (#21158)
* Add tests for booking and duration limits in getSchedule.test.ts
Co-Authored-By: keith@cal.com <keith@cal.com>
* fix: use SchedulingType enum instead of string for schedulingType
Co-Authored-By: keith@cal.com <keith@cal.com>
---------
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: keith@cal.com <keith@cal.com>
* test: add test to ensure no duplicate bookings when merging query results
Co-Authored-By: keith@cal.com <keith@cal.com>
---------
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: keith@cal.com <keith@cal.com>
Co-authored-by: Keith Williams <keithwillcode@gmail.com>
* fix: deduplicate bookings when merging results from multiple queries
Co-Authored-By: keith@cal.com <keith@cal.com>
* fix: ensure pagination works correctly when merging results from multiple queries (#21167)
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: keith@cal.com <keith@cal.com>
---------
Co-authored-by: Tushar Bhatt <95581504+TusharBhatt1@users.noreply.github.com>
Co-authored-by: Tushar <tusharbhatt0135@gmail.com>
Co-authored-by: sean-brydon <sean@cal.com>
Co-authored-by: Peer Richelsen <peeroke@gmail.com>
Co-authored-by: devin-ai-integration[bot] <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: keith@cal.com <keith@cal.com>
* feat: Add upcoming bookings feature to GET /api/bookings endpoint
- Added support for filtering upcoming bookings by adding the `upcoming` query parameter to the GET /api/bookings endpoint.
- When `upcoming` is set to "true", only upcoming bookings are returned.
- Regular users can now retrieve only their upcoming bookings by setting `upcoming` to "true".
- System-wide admins and organization admins can also retrieve only upcoming bookings by setting `upcoming` to "true".
* feat: Add status filter to booking API endpoint
This commit adds a new `status` filter to the booking API endpoint. The `status` filter allows filtering bookings by their status, overriding the `dateFrom` and `dateTo` filters. The only valid value for the `status` filter is "upcoming".
* Update _get.ts
---------
Co-authored-by: Anik Dhabal Babu <81948346+anikdhabal@users.noreply.github.com>
Syed Ali Shahbaz
Imamuzzaki Abu SalamandAnik Dhabal Babu
