Surfacing House Number Errors
A nice feature would be to surface the real error message from house number additions. Sometimes when there is a conflict between segments, you get a generic "there was an error" type message, but the back end call has the full details which you can see through dev tools. For example:
This segment: https://www.waze.com/en-US/editor/?env=usa&lon=-97.48797&lat=30.16312&zoom=6&segments=48240740
Conflicts with: https://www.waze.com/en-US/editor/?env=usa&lon=-94.82458&lat=29.82488&zoom=6&segments=48240740,511847520,511847562,511847579
When the city is listed as "none" (No City). When adding "115" to the latter, this resulted in an error (see attached)
However, the backend error that is returned by the web request is (see attached)
There's enough in the error message there to surface a link to the conflicting segment. This would help troubleshoot issues.
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=306020