Thanks for your reply. I don’t think modifying the Ruby controller is much help, since it actually obeys to the params[:limit] it is sent, so there’s no trouble there. The actual caller of the endpoint (the snippet I posted in the first post) should offer a way to customise the limit instead.
Also I’ve looked at your snippet but that particular commit (cf16264) is 4 years old (13 Apr 2018). But the latest revision still honours params[:limit].
I’m aware I can modify the values myself, but I think it would be much better to offer a user preference, or remove that limit altogether; not all organisations have development resources to make such amends, let alone run the Zammad stack themselves, so this feels like a valid bug fix/feature req to ask into the mainstream branch.
If the system enforces 50 results despite the user never explicitly asking for that limit, then the system is not behaving as expected. If the interface is not warning the user that their search is limited to 50 results, then the interface is not behaving as expected, but in both scenarios the user is left confused as to why it should be this way, and why it cannot be changed.
I’m happy to provide the code to customise this limit, if the team is willing to agree and help me merge it in.