Due to a recently added Barcelona pin, distance/date calculations are not as precise as they should - not even as they were.
Considering this, we will:
Investigate the specific pin to see if there’s wrong or missing information triggering this particular issue.
Ensure the rest of the application is working as intended.
Revise “sort by distance/date” behavior.
Steps to reproduce
Go to the menu.
Sort the pins by date or distance. A “Barcelona” one will usually appear first - and it shouldn’t, as the calculation is not correct.
Close the menu.
Go to the menu again.
Sometimes, the order is correct, but sorting the pins may trigger this error again.
Do you have any screenshots?
Code of Conduct
I agree to follow this project's Code of Conduct
Contributing Docs
I agree to follow this project's Contribution Docs
It would be interesting to design a new pin for places we’d want to visit, as the ones we have right now are limited to past experiences, but not to future events.
Suggested solution
Design new EPin image.
Create new EPinType.
Consider either making pictures optional, either including template ones related to the places we’d want to visit.
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct
Contributing Docs
I agree to follow this project's Contribution Docs
The possibility to add a music from a Spotify link that would display the title and possibly the image of the song as well as the possibility to play it within the map or via opening Spotify upon clicking.
Additional context
<3
Code of Conduct
I agree to follow this project's Code of Conduct
Contributing Docs
I agree to follow this project's Contribution Docs