Bug - Fix bbox value

[nabramow]

I was working on another branch, clicking around to make sure I didn't break anything. I noticed when I searched a location on the map, it jumped to a random unrelated place.

I replicated this on prod, so seems it's a bug. Since I recently upgraded maplibre in #5119 , I thought maybe I broke something.

But in the end seems like we were putting the bbox values in the wrong order on search?! So either this has been a longstanding issue we didn't notice or ???.

I guess the NominatumPlace could have also changed via that api call, but that also does not make sense tbh.

But hey...it works?!

Definitely test this one though in case I'm going crazy!. I tested a lot myself but I still don't understand why we had this bug to begin with.

Web frontend checklist

• [ x ] Formatted my code with yarn format
• [ x ] There are no warnings from yarn lint --fix
• [ x ] There are no console warnings when running the app
• [ x ] All tests pass
• [ x ] Clicked around my changes running locally and it works
• [ x ] Checked Desktop, Mobile and Tablet screen sizes

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
couchers	✅ Ready (Inspect)	Visit Preview	Nov 10, 2024 4:53pm

[bakeiro]

I think this is new 🙃 I tested with locations that were working nicely before and now seems they don't... I gonna check this as well!

[bakeiro]

I pushed a small commit, the dashboard needed a small fix as well