lordyavin
commented
6 months ago Currently the implementation behaves like the following. Correct me if I'm wrong, I did not code that stuff.
- An initial log entry where no quality rating is selected, does not add one for the new ascent.
- As long as there is no previous ascent of the route with quality rating, the UI does not pre-select the quality rating.
If I understood you right, you are talking about the use case to change an existing (old) ascent right? If so, it looks like the UI does not respect the case where the ascent data was loaded from the DB. In this case the UI shall clear the quality rating for the ascent as you requested.
If you previously put a quality grade on your ascent, e.g., "good", and try to unclick it and update the ascent, the API POST request is sent with the "quality" label removed from the call, which causes the ascent to not update the value at all, as seen below:
Remains the same :
For this to work, the request needs to send at least the "quality" label empty, as shown here (under privateComment), to have an impact on the ascent that you are trying to edit. This updates your ascent correctly and removes the previously selected quality.