Skip to content
This repository has been archived by the owner on Feb 20, 2019. It is now read-only.

Document the new user.search_min_length setting #4072

Merged
merged 1 commit into from
Apr 24, 2018

Conversation

settermjd
Copy link
Contributor

This PR adds a short introduction to and description of the user.search_min_length setting, so that users are aware of it. It will also be documented in the respective mobile app manuals, and in the config sample guide.

Implements

#4040.

@settermjd settermjd self-assigned this Apr 23, 2018
@settermjd settermjd requested a review from phil-davis April 23, 2018 09:25
@settermjd
Copy link
Contributor Author

@phil-davis, I'm not sure if this is sufficient. However, it seemed like the best place to document it (in the user, admin, and dev manuals). Please let me know your feedback, and I'll implement it as best as possible.

Copy link
Contributor

@phil-davis phil-davis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks a good place to add it.
See 2 comments.

From 10.0.8, user and group name search results are dependent on a new
`configuration setting`_, called ``user.search_min_length`` (it is set to 4 by
default).
This setting helps to aid search performance but requires that searches
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/searches/search

will return no results.
There is one exception, however.
If an existing user or group has a name shorter than ``search_min_length``,
then it will always be returned in the search results.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe:

Consequently, search terms shorter than the defined number of characters
will not return a list of matches. 
However, they will return an existing user or group with a name of the same
length as the search term.

(I am trying hard not to use the word "exact" because then it has to be qualified with "case-insensitive" somewhere)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome. Thanks!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That last part's more succinct than my version. It took me ages to find a description that was concise enough. Your suggestions definitely improve what I wrote.

It provides a short introduction to and description of the setting, so
that users are aware that it's in place. This will also be documented in
the respective mobile app manuals, and in the config sample guide. This
fixes #4040.
@settermjd settermjd force-pushed the document-user-match-behaviour branch from cd31cf6 to ff2042b Compare April 23, 2018 11:47
@settermjd
Copy link
Contributor Author

All changes implemented, @phil-davis

@settermjd settermjd merged commit 85d1791 into master Apr 24, 2018
@settermjd settermjd deleted the document-user-match-behaviour branch April 24, 2018 09:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants