You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a Request For Comments (RFC). It is intended to elicit community feedback regarding support for Amplify library in Flutter platform. Please feel free to post comments or questions here.
Purpose
Currently amplify-flutter library has a package amplify-core which customers use to import top level Amplify class. This amplify-core package is currently at top level and depends on all the plugin interface packages such as auth_plugin_interface making it impossible to add any base types to it which interface packages may need (creating a circular dependency between amplify-core and amplify_plugin_interface packages.
Proposed Solution
To be able to create base types in a bottom of the dependency hierarchy, we have two options:
Refactor amplify_core package
Rename the package to aws_amplify (or amplify_flutter) which will be a top level package that customers will import in their app. Use package amplify_core for adding base types and utils shared across amplify library and not used by customers.
This will be a breaking change for current developer preview customers as they will now import amplify as:
This issue is a Request For Comments (RFC). It is intended to elicit community feedback regarding support for Amplify library in Flutter platform. Please feel free to post comments or questions here.
Purpose
Currently
amplify-flutter
library has a packageamplify-core
which customers use to import top levelAmplify
class. Thisamplify-core
package is currently at top level and depends on all the plugin interface packages such as auth_plugin_interface making it impossible to add any base types to it which interface packages may need (creating a circular dependency betweenamplify-core
andamplify_plugin_interface
packages.Proposed Solution
To be able to create base types in a bottom of the dependency hierarchy, we have two options:
Refactor
amplify_core
packageRename the package to
aws_amplify
(or amplify_flutter) which will be a top level package that customers will import in their app. Use packageamplify_core
for adding base types and utils shared across amplify library and not used by customers.This will be a breaking change for current developer preview customers as they will now import amplify as:
Keep
amplify_core
as top level and create another package for base typesThis new package can be called
amplify_base
. This will not be a breaking change immediately and customers will use amplify library asLet us know in comments if you prefer one way or the other or it doesn't impact you.
Appendix: Other Amplify platforms
JS
iOS
Android
The text was updated successfully, but these errors were encountered: