Make the system users list searchable - #397
Open
level09 wants to merge 2 commits into
Open
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Salvaged from the closed #217 and rebuilt on current main.
The System Users page has no way to find a user. It turns out this is not a missing feature so much as a broken one on both ends:
{search: this.search}as the second argument toapi.get(), which axios reads as the request config, not as params. An unknownsearchkey there is silently dropped, andthis.searchwas never defined on the component in the first place. Nothing was ever sent.qparam all along, soqwas dead code that nothing could reach.Changes
clearable,@click:clear="resetSearch", submit on Enter) so it behaves the way the other admin lists already do.refresh()now sends real query params via the axiosparamsobject.qmatches name, username, or email instead of name alone. Case-insensitive partial match.Permission note
usernameandemailare masked by thesecure_*properties for users withoutview_usernames, so letting them search those fields would be an enumeration oracle: no email is visible, but a hit or miss reveals whether one exists. The broadened search is therefore gated on the same condition the masking uses (Adminorview_usernames); everyone else keeps matching onnameonly, exactly as before.test_hidden_identifiers_are_not_searchablecovers this, and fails if the gate is removed (verified).Verification
Not included
Status and role filters. #217 had them, but they are a filter-row design decision on a page Daniel owns, and there is no ticket or mockup driving them yet. The search field is the unambiguous part and stands on its own. Worth raising with him against BYNT-1549.