-
Notifications
You must be signed in to change notification settings - Fork 154
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃殌 Feature: Unify Dart and Flutter Package #588
Comments
Thanks for raising this issue! 馃檹馃徏
Can you expand more on the boilerplate? |
I created abstract API class which has basically the same methods like database,account,team and so on. Then I have a singelton Class which holds an instance of the API that is given over an Init method. In Server functions I created an Implementation of the API class that uses dart_appwrite package In Client code I created an Implementation of the API class that uses appwrite package |
We did this split for a few reasons:
|
馃敄 Feature description
At the moment we have different SDKs for Backend (Dart) and Frontend (Flutter). This is not optimal for people who want to reduce their boilerplate code.
For example if someone want to use the same strongly typed data models in functions like he does in the frontend he is forced to write a lot of Boilerplate code to first generalize the API calls in a Package and then again define specific for the appwrite packages in a Server Package and Client Package again.
馃帳 Pitch
My Idea is to create a Dart SDK booth used by Dart and Flutter and then one Specific Flutter SDK which is only used by Flutter.
In the specific Flutter framework only things like OAuth or other Frontend Specific things are defined.
This can be done b using Mixins in the Flutter SDK.
馃憖 Have you spent some time to check if this issue has been raised before?
馃彚 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: