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: Add 'kakao' to Provider type #720

Merged
merged 1 commit into from
Jul 2, 2023
Merged

feat: Add 'kakao' to Provider type #720

merged 1 commit into from
Jul 2, 2023

Conversation

kim-taewoo
Copy link
Contributor

@kim-taewoo kim-taewoo commented Jul 2, 2023

What kind of change does this PR introduce?

This PR adds 'kakao' to Provider type.
Kakao provider was recently added to supabase/gotrue through this PR(document has also been updated. PR)

What is the current behavior?

IDE warns type error because there is no 'kakao' in Provider type.
image

What is the new behavior?

'kakao' added properly in Provider type, so no error shown in IDE

Additional context

Please let me know if I have to change anything to be approved. Thank you!

@hf
Copy link
Contributor

hf commented Jul 2, 2023

Thanks for this. I'll approve but the dashboard changes go in next week.

@hf hf merged commit ef16123 into supabase:master Jul 2, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Jul 2, 2023

🎉 This PR is included in version 2.38.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@kim-taewoo kim-taewoo deleted the kim-taewoo/kakao-provider-enum-type branch July 2, 2023 15:57
@kim-taewoo
Copy link
Contributor Author

Thanks for this. I'll approve but the dashboard changes go in next week.

@hf
Hi hf! Could you tell me what dashboard means? I guess you are saying this PR changes will be applied next week when supabase-js is deployed, but not sure how things work in supabase community. Anyway, thanks for the quick response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants