You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 26, 2020. It is now read-only.
Elasticsearch is used to get the trending ideas/projects but there is a problem with these queries. They both do a search for all ideas AND projects and assume that what they get back is a list of IDs for only ideas OR projects, whichever page you are coming from. This is not the case. The list of IDs includes both ideas and projects, but the whole bunch is assumed to be all ideas (if you're on the ideas page) or all projects (if you're on the projects page).
For example, on the ideas page the trending search might return IDs 1, 12, 20, 35, and 55. But ID 12 is actually a project object! However, the page assumes they are all ideas, so will return idea 12 in the list of results, but it has nothing to do with the actual results!
The trending queries need to explicitly say what object type they want to get back.
Elasticsearch is used to get the trending ideas/projects but there is a problem with these queries. They both do a search for all ideas AND projects and assume that what they get back is a list of IDs for only ideas OR projects, whichever page you are coming from. This is not the case. The list of IDs includes both ideas and projects, but the whole bunch is assumed to be all ideas (if you're on the ideas page) or all projects (if you're on the projects page).
For example, on the ideas page the trending search might return IDs 1, 12, 20, 35, and 55. But ID 12 is actually a project object! However, the page assumes they are all ideas, so will return idea 12 in the list of results, but it has nothing to do with the actual results!
The trending queries need to explicitly say what object type they want to get back.