feat: added project id from the results returned by the search endpoint#3902
feat: added project id from the results returned by the search endpoint#3902
Conversation
Signed-off-by: Efren Lim <elim@linuxfoundation.org>
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
3 similar comments
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability. Example:
Projects:
Please add a Jira issue key to your PR title. |
|
@emlimlf @gaspergrom is this something that's still needed? It wasn't reviewed and it seems that it's stale. If this is already in production, let's make sure we merge this |
In this PR
Added the project id from the results returned by the search endpoint. This will be used by the create collection since it requires the ID instead of the slug
Ticket
IN-1010
Note
Medium Risk
Alters the search endpoint response schema by adding a new column, which may require coordinated updates for downstream consumers that assume a fixed column set/order.
Overview
Updates
search_collections_projects_repos.pipeto include a newidcolumn in the unified search response, populating it frominsightsProjects_filtered.idforprojectresults and returning an empty string forcollectionandrepositoryrows.This changes the output schema/order for the search pipe consumers while keeping filtering, ordering, and limits the same.
Written by Cursor Bugbot for commit 60c144a. This will update automatically on new commits. Configure here.