Skip to content

Use id_in to avoid Rubocop warnings

What does this MR do and why?

Describe in detail what your merge request does and why.

This MR replaces where(id: ) calls with id_in. id_in is a drop-in replacement for where(id: ) which doesn't trigger a warning.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

This MR does not change any logic, so we only need to check that the tests pass.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports