Open camilasan opened 3 months ago
By doing this are we not wiping away ay errors that need actions from users?
I also don't see how this fixes the errors referenced in the PR post; it seems to me we should be more lenient in how we tolerate post-device-wake-up errors in the client, rather than changing how errors are presented
Yes, I am still thinking on how to properly/correctly approach this.
Failed conditions
C Maintainability Rating on New Code (required ≥ A)
6 New Code Smells (required ≤ 0)
See analysis details on SonarCloud
Catch issues before they fail your Quality Gate with our IDE extension SonarLint
AppImage file: nextcloud-PR-6831-e57556138b75a1e579ea0a79db6cd89ef9286632-x86_64.AppImage
To test this change/fix you can simply download above AppImage file and test it.
Please make sure to quit your existing Nextcloud app and backup your data.
Failed conditions
0.0% Coverage on New Code (required ≥ 80%)
B Maintainability Rating on New Code (required ≥ A)
8 New Code Smells (required ≤ 0)
See analysis details on SonarCloud
Catch issues before they fail your Quality Gate with our IDE extension SonarLint
Possible fix for #6448 and #6487.