As I am debugging prose-im/prose-pod-api#331, I realized I might have been mislead by the Dashboard when I did my manual tests before pushing my fix.
When I toggle s2s for example, the UI is shown as if everything went well (i.e. green toggle + nothing else), but after a few seconds the API database times out and the API sends a 500. The Dashboard then crashes and reloading the page shows the setting as not changed.
I have seen that there is an alert saying “Changes saved”, but I feel like their should still be a loading indicator. I did not know there was such alert therefore I wasn’t looking for it when making changes.
Could we have a loading indicator next to config inputs (universal solution) or more custom UI like for toggles a transition state?
While the API shouldn’t have those kinds of bugs and I will do my best to fix all of the obvious ones with a future-proof design, I still think this would be great in terms of UX.
As I am debugging prose-im/prose-pod-api#331, I realized I might have been mislead by the Dashboard when I did my manual tests before pushing my fix.
When I toggle s2s for example, the UI is shown as if everything went well (i.e. green toggle + nothing else), but after a few seconds the API database times out and the API sends a 500. The Dashboard then crashes and reloading the page shows the setting as not changed.
I have seen that there is an alert saying “Changes saved”, but I feel like their should still be a loading indicator. I did not know there was such alert therefore I wasn’t looking for it when making changes.
Could we have a loading indicator next to config inputs (universal solution) or more custom UI like for toggles a transition state?
While the API shouldn’t have those kinds of bugs and I will do my best to fix all of the obvious ones with a future-proof design, I still think this would be great in terms of UX.