Remove users from classes - No conditional logic for single vs multiple classes

[pcenov]

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Observed behavior

Observed by @radinamatic: If the learners are enrolled in only 1 class, and we want to remove them, what is the purpose of the Search for a class field, and the Remove from all classes checkbox...?
In my mind these would make sense only if learners are enrolled in more than one class.

Expected behavior

Should be further discussed.

Steps to reproduce the issue

1. Install the build from 0.19 string freeze updates #13925
2. Go to Facility > Users and select a user or several users enrolled in a single class
3. Click the 'Remove from class' icon

Usage Details

Windows 11, Ubuntu 22, Mac OS 15.5 - Chrome, Firefox

[pcenov]

@radinamatic

[nucleogenesis]

My suggestion here is that we should we make SelectableList handle the case of "only one item in the list given" so that it doesn't show a "Select all" or a "Search" input at all and shows the one option in a single cell.

I don't think this particular case of only one class being in the list needs any special design consideration. As-is it's mostly just a strange looking design that is functional without being too confusing (IMO anyway).

@AlexVelezLl @marcellamaki would appreciate your thoughts and I'll update the issue sometime before EOY at an issues writing meet.

[AlexVelezLl]

Makes sense to me, @nucleogenesis. I didn't find a case where we would like to have the Selectable List with just one item, with the search and select all nodes being rendered, so it'd make sense to update the SelectableList component directly for these cases imo.