• Better typesense 0.24.1 support
• Exhaustive search disabled by default
• Added central place for the MAX_RESULTS_PER_PAGE option
  • In the future we should strive for the "options" pattern, where a class represents the configuration options of the app and applies safe defaults in the correct type.
  • Added max_results_per_page() helper function as part of this fix.
• Added class for getting searchable attributes of models in typesense
• Added basic search analytics:
  • The default implementation saves the search terms and the first page of hits and hit count in the database, and indexes the search term in Typesense.
  • Indexing the search terms used by users will later help with adding new features. (E.g. search suggestions)
• Fixed tests
• Fixed an issue with the /v4/schedules/<dayFilter> request validator.
• Fixed deprecation logger
• Fixed bug with ordering through the search engine. E.g. ?q=searchterm&order_by=score would not order by score, rather by the default sort order.
• Fixed 🐛 Looking up some profiles or user with uppercased username will throw 404 #411

Exhaustive search disabled means that typesense will eat less system resources, but the number of hits will decrease, but the quality of relevance won't be affected.
I think with earlier versions of typesense we used exhaustive search to have enough hits. However the latest version already returns enough hits with exhaustive search turned off for most of the use cases. Only the drop_tokens_threshold and typo_tokens_threshold needs to be tweaked, and we can get good enough results I think.

Might fixes these issues:

• Search upstream times out  #393
• 🐛 Searching for "Ninjala" returns results for "Ninja" #401
• Wrong searching process #396