Closed zstadler closed 3 years ago
This also causes the queue to get stuck... Related to #1477
Causing the queue to get stuck will be solved in #1477, UX of error when uploading a POI will be handled here. Reducing severity.
@zstadler I can't think of a good UX to solve this... :-( The only idea I have is to change the message text to something like "thanks for contributing, the data will be checked and uploaded if it's valid" and change the toast color from green to black. The upload may happen instantly or after a few hours depending on the internet connecting so popping up a message according to response from server doesn't feel like a solution for me. Allowing the user to somehow amend his upload in case of a problem is a huge effort with little value as I think this can happen only to gates right now... If you have an idea for a solution please let me know...
MHO, from a UX perspective,
In the above proposal I also considered the potential need to handle errors in other types of uploads, not only barriers, given the offline-first approach.
While it's possible and I think it's s good way to show these errors, it would require a lot of effort with very limited value. I would like to try and think about a far less complex implantation to solve this. I'll mark this issue as "need discussion" and we'll take this offline. As to other uploads, currently all know limitations are handled in the client side so in theory, besides gates, upload should not fail.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days
As far as we know, barrier POIs are not inserted only when a highway
way cannot be found within the search radius.
In this case, rather than not inserting the barrier, it should be inserted at the report location, disconnected from any OSM way. This operation is no different than a similar operation using an OSM editor.
As a result, there is no loss of an edit and no need to inform the user of a failure to insert a barrier.
Bug
What I expect to happen
See an error message when a barrier POI cannot be created
What really happened
Received a confirmation message
What I did that caused the issue - step by step
There are several senaries where a barrier cannot be created. Here is an unrealistic example for simplicity.