[openstreetmap/openstreetmap-website] Use where instead of find to prevent 404 (b9c85c2)

[Kamil Monicz]

If the majority consensus leans toward accepting the sacrifice of backward compatibility in the name of optimization, then let it be so. Thank you for the clarification.

My concern regarding optimization pertains specifically to this commit, not the other sorting-related change. This change specifically didn't introduce fresh functionality; it merely enhanced efficiency, as evidenced by [my previous code](https://github.com/openstreetmap/openstreetmap-website/commit/b9c85c269726faad3c2613b37f01683c8b59f5c6#commitcomment-125594991). While I wholeheartedly support this modification, I firmly believe it should not have been executed in a manner that breaks compatibility. This, I perceive, is a lack of consideration for developers who utilize this API.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/commit/b9c85c269726faad3c2613b37f01683c8b59f5c6#commitcomment-125691393
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/commit/b9c85c269726faad3c2613b37f01683c8b59f5c6/125691393 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20230828/77630d6c/attachment.htm>