Replacing a no-op confirm with a promise means every exit now owes somebody an answer

Munchable's confirm dialogs used to be Alert.alert. On react-native-web that export is literally class Alert { static alert() {} }, so every confirmation in the browser build did nothing at all: sign out, delete account, the report flow. I wrote that one up already. The replacement is a small store plus a host component, and it works on all three platforms. This post is about the bug the replacement is capable of, which has the same symptom as the one it fixed. A promise is a debt The API that r

Read the full article: https://dev.to/daniel_pertu/replacing-a-no-op-confirm-with-a-promise-means-every-exit-now-owes-somebody-an-answer-4bke

Source: DEV Community