Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(supabase): add supabase integration #418

Merged
merged 26 commits into from
Sep 20, 2024
Merged

feat(supabase): add supabase integration #418

merged 26 commits into from
Sep 20, 2024

Conversation

tshedor
Copy link
Collaborator

@tshedor tshedor commented Aug 26, 2024

Addresses #359 and #401

@tshedor tshedor changed the title feat: add supabase integration feat(supabase): add supabase integration Sep 6, 2024
@tshedor tshedor marked this pull request as ready for review September 19, 2024 16:40
@Doetheman
Copy link

Supabase integration pretty dope. Flutterflow may be interested in using this

Copy link
Collaborator

@mateominato mateominato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not to be confused with superhot

@@ -0,0 +1,13 @@
## Unreleased
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

intended header?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it's sort of the always-present header that catches new stuff. It's a convention in all of the CHANGELOG files. I had a good reason for at some point but now couldn't tell you why

@tshedor tshedor merged commit b925741 into main Sep 20, 2024
22 checks passed
@tshedor tshedor deleted the supabase-integration branch September 20, 2024 02:24
@tshedor tshedor mentioned this pull request Sep 20, 2024
29 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants