**What** The actual behavior is that the skip/take is applied in a first query returning the correct number of results. When there is no relations, we are calling findByIds with the previously retrieved ids, but we also pass skip/take which means that no result are returned after the first increment of the skip. The skip/take should not be applied in that case as it has already been applied. FIXES CORE-970
143 B
143 B
@medusajs/medusa
| @medusajs/medusa |
|---|
| patch |
fix: Custom repository take/skip wrongly applied when there is no relations in the findWihtRelationAndCount