Bookings: Update selector for service/event and customer name filters

[itsmeichigo]

Part of WOOMOB-1240

Description

This PR updates the selector for Service/Event and Customer name filters for bookings:

• Adds a new type conforming to ListSyncable to support showing selector for bookable products (named as Service/Event on the UI).
• Updates the Customer selector:
  • Renames the title to match the filter option for bookings
  • Updates the navigation to use push instead of modal.
  • Adds new configuration for the presentation type to ensure that the selector is still presented modally from order creation form.
  • Update UI for the customer rows to better match the design. I'm keeping the search bar for simplicity.
  • Avoid dismiss selector upon selection. We'll need to support multiple selection in a subsequent PR.

Testing steps

• Log in to a CIAB site with existing bookings.
• Navigate to Bookings > All > Filter.
• Select Service/Event and confirm that only bookable products are displayed. Selecting any option should show a checkmark next to the option. Dismissing the view should display the product name on the filter screen.
• Select Customer name and confirm that the customer selector is pushed from the same navigation stack.
• Confirm that the customer selector has the correct title and selecting any option would show a checkmark next to the option. Dismissing the view should display the customer name on the filter screen.

Testing information

• Tested and confirmed with simulator iPhone 17.
• Also checked the customer selector on Order filter and Order creation form and confirmed that no regression was made.

Screenshots

Simulator.Screen.Recording.-.iPhone.17.-.2025-10-27.at.14.34.02.mov

---

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce iOS Prototype by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce iOS Prototype
	Build Number	pr16278-b6ed021
	Version	23.5
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	b6ed021
	Installation URL	7c89kbs94j4lo

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[adborbas]

Hi @itsmeichigo, There might be something I'm missing, but I could not get the selections dismiss working.

Case	Recording	Description
Service / Event selection		Selection does not dismiss the view
Customer selection		Selection does not dismiss the view
No name customer selection		Selecting a "No name" customer after a "No name" customer changes the order. Also, there is no option to clear selection

[itsmeichigo]

Thanks @adborbas for the feedback!

I could not get the selections dismiss working.

I just updated all the filters for bookings in this PR to not dismiss the selector immediately upon selection. This will keep the behavior consistent with the static options as well (attendance status, booking status). Also we'll need to support multiple selections, but that will be handled later. So for now, one would need to either tap < arrow to add more filter or tap Show bookings to apply the filters.

Selecting a "No name" customer after a "No name" customer changes the order.

I updated the sort descriptor in fb76687 to fix this.

there is no option to clear selection

I asked Wagner in lxixW6aBBNkCd9ooBK70Z1-fi-1421_3698#1478520395 - I'll update this later when I get a response from him.

[adborbas]

I just updated all the filters for bookings in this PR to not dismiss the selector immediately upon selection.

@itsmeichigo Ok, thanks for the clarification! This makes sense now.

In this case I think the "Testing steps" needs some adjustment cause it says:

• "Selecting any option should dismiss the view and display the product name on the filter screen."
• "Selecting any option would dismiss the view and display the customer name on the filter screen."

I'd expect them to say not dismiss the view.

I'll check the code now.

[adborbas]

Nice work on this 👍 Had one small comment.

[adborbas]

One small concern — I wonder if we really need to store the entire Product here. Having both product, id, and name feels a bit redundant and might make it easier for other parts of the code to start depending on BookingProductFilter for full product data instead of just treating it as a lightweight filter value.

Would it make sense for this type to only keep the minimal info needed for filtering (e.g. id and name) and drop the product property? That would keep the model focused on its purpose and avoid any unintended coupling later on.

[itsmeichigo]

This is a valid point! I added an update in b6ed021 with the following changes:

• Removed the full product model from BookingProductFilter.
• Updated SyncableListSelectorView to accept a closure for checking initial selection rather than comparing full models.
• Updated FilterListViewController following the selection logic change.

[itsmeichigo]

I'd expect them to say not dismiss the view.

My bad, I updated the code but forgot to update the PR description. I updated it to avoid confusion in case someone else visits the PR.

I just addressed the issue you found above, will enable automerge now to unblock my other PR. Please feel free to leave comments if any, I'll address them in subsequent PRs.

Thanks!