fix: prevent API calls for whitespace-only search input

[thisisharsh7]

Fixes Issue

Closes #347

What's the problem?

You can type just spaces into the waypoint search field and it'll actually make an API call. The API returns a 400 error saying "Nothing to search for", which is correct, but we shouldn't be making that call in the first place.

Why does this happen?

The code checks if the input length is greater than 0 before searching:

if (internalValue.length === 0) return;

But " ".length is 3, not 0, so it passes the check and triggers the API call.

The fix

Added .trim() before checking the length in a few places:

1. Before making the API call
2. Before checking if we should search on Enter key
3. When sending the value to the geocoding API

Created a trimmedValue variable to avoid calling .trim() multiple times:

const trimmedValue = internalValue.trim();

Testing

• Type only spaces → No API call
• Type actual location → Works normally
• Type location with leading/trailing spaces → Gets trimmed, works

---

Note: This PR was created with AI assistance. I discovered the bug through manual testing, and AI helped with debugging. I've reviewed, understood, and verified the fix works as expected.

[ghost]

Preview is ready! 🚀 You can view it here: https://valhalla-app-tests.gis-ops.com/352