Merge request list GraphQL should filter labels using same key as issues list
Context
The Merge Requests GraphQL resolver allows for filtering by labels
.
However, because this key (labels
) differs from the Issues list resolver implementation (labelName
), none of the filter tokens or existing implementation work with it.
Problem
While we could build entirely new filter tokens and other integrations with the search bar to work with the labels
name, it seems like the more efficient fix would be to match the issues key name (labelName
) rather than duplicate all of the front end code.
Notably: the merge request implementation does have as: :label_name
, but this does not appear to allow labelName
in the GraphQL based on testing.
Fix
As noted, we (frontend) could duplicate the Labels filter token and replace the labelName
filter keyword with labels
, but this seems backward: if the merge request GraphQL resolver changes its naming scheme to labelName
(or label_name
), everything already written will start working.