Pagination of primary action breaks showing relationships
I think I may have found a bug.
I have resources A and B with a many_to_many relationship. I edited the primary read action of
B to make it require pagination with required?: true. This is because I wanted to make it so that even if someone calls my API without a limit, the default limit per page is still applied.
But now, when I go to A in the Admin UI, click on a row, then click the button to load its related Bs, nothing happens. No SQL query is executed. When I un-require the pagination, then it works. Yet, when I click the second button that only shows the IDs of the rows of the "join_through" resource, that one works.
Is this intentional?1 Reply
🤔 sounds like no
Can you open a bug?