New extension: Supabase

[github-actions]

Description

This extension is an upgrade of Supabase save state extension #1067 by @romw314.

Supabase vs Supabase save state

• Both, Supabase and Supabase save state, use the same JavaScript client by @romw314.
• Supabase doesn't need a static scheme (setup), however, extension users still need to configure their own Supabase projects.
• Supabase supports OTP authentication.
• Supabase supports CRUD and filtering.
• Supabase retrieves session automatically by saving/loading refresh token.

Comparison

How to use the extension

• Get project's URL and key from Supabase.
• Open the extension in the editor and set SupabaseURL and SupabaseKey.
• On Supabase.com, currently you have to let anonymouses read tables, no need to let anonymouses create/update/delete.

Checklist

• I've followed all of the best practices.
• I confirm that this extension can be integrated to this GitHub repository, distributed and MIT licensed.
• I am aware that the extension may be updated by anyone, and do not need my explicit consent to do so.

What tier of review do you aim for your extension?

Community (Unreviewed)

Example file

Supabase example.zip

Extension file

Supabase.zip

[EyadMahm0ud]

Oh no.
Do I really have to add exception?

[romw314]

Yes, that's ok. And, if you want them to check the client, use the unminified version of the client that I built: https://gist.github.com/romw314/42184c41bc21fca206856a446c9e77b1

[EyadMahm0ud]

Thanks, @romw314. I will use it.
Moreover, I noticed that the extension is spaghetti, so I will rewrite some of the actions.

[EyadMahm0ud]

!update
Supabase.zip

---

What's New? (0.9.0 » 1.0.0)

• Use a non-minified version of the code for easy review, thanks @romw314.
• Support for new variables system.*
• Support callback variable with "state", like Firebase.*
• Support filters and modifiers.
• Storage support. Delayed

Please note that most functions have become two (JavaScript & Standard Events) to support both.

[EyadMahm0ud]

I don't really know how to add exceptions for the extension.

[EyadMahm0ud]

!update
Supabase.zip

• Better and more consistent event sentences/descriptions.

[EyadMahm0ud]

!update
Supabase example.zip

[github-actions]

❗ An internal error has occurred. See logs at https://github.com/GDevelopApp/GDevelop-extensions/actions/runs/11077373026.

[romw314]

!update Supabase example.zip

You shouldn't post the example using !update. Just post it because that's only for the GD extensions team, not for the automation.

[github-actions]

❗ An internal error has occurred. See logs at https://github.com/GDevelopApp/GDevelop-extensions/actions/runs/11083023031.

[romw314]

❗ An internal error has occurred. See logs at https://github.com/GDevelopApp/GDevelop-extensions/actions/runs/11083023031.

Oh no, my quote of the !update has started the automation pipeline.

[github-actions]

❗ An internal error has occurred. See logs at https://github.com/GDevelopApp/GDevelop-extensions/actions/runs/11106717584.

[romw314]

❗ An internal error has occurred. See logs at https://github.com/GDevelopApp/GDevelop-extensions/actions/runs/11106717584.

Again? 😆

[romw314]

I don't really know how to add exceptions for the extension.

Hi, @EyadMahm0ud, to add the exception, follow these steps:

Fork this repo but disable copy only master branch, create a new branch from the extension/EyadMahm0ud/1376 branch, add the exception into scripts/lib/ExtensionsValidatorExceptions.js in the new branch, and create a new PR from the new branch in your fork to the extension/EyadMahm0ud/1376 branch in this repo. After the GDevelop staff merges the PR you created to add the exception, CircleCI should pass.

For your next extensions, I recommend you creating the PR to submit the extension manually.