[wp-meta] [Making WordPress.org] #5228: Consistency tool: create wildcard search option

[Making WordPress.org]

#5228: Consistency tool: create wildcard search option
--------------------------------------+---------------------
 Reporter:  felipeloureirosantos      |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  low                       |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:
 Keywords:  dev-feedback has-patch    |
--------------------------------------+---------------------

Comment (by felipeloureirosantos):

 Replying to [comment:3 dd32]:
 > Adding a wildcard here isn't out of the question, but it's not super
 performant.
 >
 > Due to the number of strings in the DB adding a suffix wildcard (ie.
 `Drop-in%`) is about 10x slower, and while it works, it's not going to
 scale.

 That makes total sense. I expected something like that as it would bring
 really more strings.

 I see that it would make the tool really more useful as it would allow us
 to have context on the translation and show other possible translations
 for the same word, but I personally believe that it could be cached for a
 long period.

 Do you believe that cache the results for like 30 days would make sense?
 Would that help in this situation?

 In this case, maybe would be a good idea adding a message there like that:
 "Results from [DATE]"

 > We'd have to limit it to logged in users only, and probably best even
 only to those who have some form of higher permissions than a translation
 contributor (which shouldn't be a problem).

 I totally agree regarding logged in users only, but could we limit the
 number of wildcard searches that the users could have instead of limiting
 to PTE/GTE only?

 It would be amazing for providing consistency tool links on new
 contributors' strings reviews, and also for them being able to do that
 themselves.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5228#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org