It happened to me I deleted a column that had a foreign key constraint and for someone not working with databases, I didn't know it is a nono. It resulted in having multiple foreign keys after I added a new one to replace it.

Maybe we could either prevent it or warn the user that the foreign key should be first removed on the dropped column? Or remove the constraint with the column? Also, why c

https://emotion.sh/

After this change in Material UI: mui-org/material-ui#6115

Could you please add same text from Cloud Function emulators to firestore one:

https://firebase.flutter.dev/docs/functions/usage/#emulator-usage

I spend hours trying to figure out why my app does not write to emulator...and it was caused by missing plist/manifest settings allowing insecure HTTP communication :(

Summary

Add basic pre-commit hooks to the repo. To catch, for example, broken symlinks (WorldHealthOrganization/app#1670)
Link: https://github.com/pre-commit/pre-commit-hooks

Possible config file. Should be run against every file in the existing tree to see what issues might come up.

# .pre-commit-config.yaml
-   repo: https://github.com/pre-commit/pre-comm

The problem faced currently?

While adding an ingress route, or a target in ingress route.
If by mistake white space gets added to the route or host. We get the error specified route not found or unable to reach the specified target

How can we solve it?

Mission control should remove the white space if present before saving the config

If you want this feature to be implemented, gi