Improve documentation

Link

Edge Deploy Guide

Describe the problem

Guide says:
supabase functions deploy hello-world

Dashboard Function page says:
supabase functions deploy hello --project-ref ugccqefilvseqbseypbq

Describe the improvement

They should be the same and which ever method is correct

🚀 Feature

(A clear and concise description of what the feature is.)

Have you spent some time to check if this issue has been raised before?

(Have you googled for a similar issue or checked our older issues for a similar bug)
Yes

Have you read the Code of Conduct?

Yes

Pitch

A common way to mana

Please describe your documentation issue or suggested improvement in detail here and provide links to any pre-existing/relevant documentation and screenshots if necessary:

The link to the docs is broken, the current link is:
https://firebase.flutter.dev/docs/dynamic-links/usage

The correct link is:
https://firebase.flutter.dev/docs/dynamic-links/overview

Thanks.

The current implementation of the maps API lacks support for the snapshot() functionality.

https://github.com/microg/GmsCore/blob/master/play-services-maps-core-mapbox/src/main/kotlin/org/microg/gms/maps/mapbox/GoogleMap.kt#L483

This is a requirement for location sharing in Signal messenger.

https://emotion.sh/

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

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

When we create a new table using an existing table config, it doesn't copy its children tables' configurations.

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