-
Notifications
You must be signed in to change notification settings - Fork 2
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
[DRAFT] Full network support #216
Conversation
remoteConfigService.clientId, | ||
CognitoUserPool userPool(Network network) => CognitoUserPool( | ||
remoteConfigService.userPoolId(network), | ||
remoteConfigService.clientId(network), | ||
); | ||
CognitoUser? cognitoUser; | ||
CognitoUserSession? session; | ||
|
||
RemoteConfigService get remoteConfigService => eosService.remoteConfigService; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this should be a single network specific object with all the ppp parameters in it.
@@ -104,23 +104,23 @@ class RemoteConfigService { | |||
String get accountCreatorEndpoint => FirebaseRemoteConfig.instance.getString('accountCreatorEndpoint'); | |||
|
|||
// PPP Service AWS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the below methods should be a single network specific object with all the ppp parameters in it.
For your review
Seems like we could do something more elegant than using "network" everywhere
For example we could pass it around instead of accountName
The problem is now that network is stored in user profile, and I am not sure we always have one
If we always have one then we could always pass around a user profile, or an object with only accountName and network everywhere, and not have this parameter pollute the whole code base.
IDK