feat: Add back searching in disabled user list#45370
Conversation
Implemented.
I think this is fine, because a class implementing the interface for 30 also implements the one for 28.0.0, as it’s only a new parameter. |
|
/compile / |
provokateurin
left a comment
There was a problem hiding this comment.
I would prefer separate methods for searching quite a lot over changing the behavior of the existing methods. Would that be possible or is it too much work or impractical?
|
Ok in light of the discussion in #44936 it makes sense to extend the existing endpoint instead of creating a new one |
When disabled users where moved to their own endpoint we overlooked search, so adding it back. The search is done case-insensitive in uid and display name. Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
To match what is done for Database backend for enabled users Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
bfde1f7 to
0505a1f
Compare
|
/compile / |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
e5c0dbb to
9a523e9
Compare
|
/backport to stable29 |
|
/backport to stable28 |
Summary
When disabled users where moved to their own endpoint we overlooked search, so adding it back.
The search is done case-insensitive in uid and display name.
TODO
Checklist