Well… a couple of things that could be done better in that example: —⁂— const [data, setData] = useState<Array<Array<object>> | undefined>(); That type sti

Well… a couple of things that could be done better in that example: —⁂— const [data, setData] = useState<Array<Array<object>> | undefined>(); That type stinks. Kill the undefined bit by giving it an initial value, then you can skip the `?? []` later too; and replace Array<object> with the actual row type, probably naming it, maybe like this: type Record = [string, number, number, number, number]; const [data, setData] = useState<Record[]>([]); —⁂— const params = Object.entries({ aroma, flavor, acidity, sweetness }) .map(([k, v]) => `${k}=${v}`) .join("&"); No need to construct the query string manually: const params = new URLSearchParams({ aroma, flavor, acidity, sweetness }); I confess I’m puzzled about this one too, as trailbase.js suggests you know about URLSearchParams, which is what you should use for all typical query string manipulation, parsing and generation.