I noticed that there is no ideal way of (fuzzy) searching boards and items using the GraphQL API.
We are building several apps where we need the end-user to select items or boards.
For a board picker, we keep fetching all boards, using the pagination arguments, until we have found 20 boards that match the user’s input. (board-name includes the input string)
For an item picker, we first ask the user to select a board, using the strategy above, and then we keep fetching all items, using the pagination arguments, until we have found 20 items that match the user’s input. (item-name includes the input string)
- Are very slow when the monday.com instance has lots of boards and items.
- Do not scale with the complexity budgets in the api.
Preferably, we would love to be able to query boards and items using a
search argument so that we do not need to fetch all items to find the item the end-user is looking for.
Is our approach the only way to make this work, or am I missing something?