Skip to content
This repository was archived by the owner on May 13, 2023. It is now read-only.

Conversation

@dshukertjr
Copy link
Member

What kind of change does this PR introduce?

Currently, it is unclear to Flutter developers whether they should use supabase or supabase_flutter package. This PR aims to clearly direct the Flutter devs to use supabase_flutter.

@dshukertjr dshukertjr changed the title chore: chore: Update readme to direct Flutter developers to use supabase-flutter Oct 24, 2022
@dshukertjr dshukertjr requested a review from Vinzent03 October 24, 2022 07:05
@Vinzent03
Copy link
Contributor

Why do you remove the auth section?

@dshukertjr
Copy link
Member Author

@Vinzent03
I thought it could be another reason why people could use this package instead of supabase_flutter for Flutter apps. There is a simple auth section above it already, so I thought no need to add a deep dive into auth in this library.

Most of the people that land on this page are Flutter developers, and they should go here. Server side Dart users can and should use this package, but client side auth method are not relevant to them. The only users that detailed auth section is relevant to would be Angular Dart users as far as I can think, and I think it's a small enough number of users that I think we can ignore.

Copy link
Contributor

@Vinzent03 Vinzent03 left a comment

Choose a reason for hiding this comment

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

Makes sense

@dshukertjr dshukertjr requested a review from Vinzent03 October 24, 2022 08:15
@dshukertjr dshukertjr merged commit b00f894 into main Oct 24, 2022
@dshukertjr dshukertjr deleted the chore/readme branch October 24, 2022 08:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants