Skip to content

loads legacyindex only if search is used

chandi requested to merge reduce-legacyindex-requests into master

What does this MR do?

currently there is /api/search/legacyindex loaded on every page load, which includes multiple mysql queries. Since it is not used so often, we should rather load it on demand.

How confident are you it won't break things if deployed?

pretty

Checklist

  • added a test, or explain why one is not needed/possible...
  • no unrelated changes
  • asked someone for a code review
  • joined #foodsharing-beta channel at https://slackin.yunity.org
  • added an entry to CHANGELOG.md (description, merge request link, username(s))

Merge request reports