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

Adding documentation and validations in OnboardingService.dart #946

Open
sitaram-kalluri opened this issue Nov 22, 2024 · 2 comments
Open
Labels
bug Something isn't working

Comments

@sitaram-kalluri
Copy link
Member

sitaram-kalluri commented Nov 22, 2024

Which at_widget package you find issue with?

at_onboarding_flutter

On what platforms did you experience the issue?

Android, iOS, Windows, MacOS, Linux

What version are you using?

at_onboarding_flutter : 6.19

What happened?

  1. Add documentation to the OnboardingService.authenticate method to clearly define its purpose and behavior.
  2. Add parameter validations in OnboardingService.authenticate method for cramSecret and jsonData as they are mutual exclusive.
  3. In the OnboardingService.onboard method, propagate the rootDomain from the AtClientPreferences to the rootDomain in the AtOnboardingRequest.
@XavierChanth
Copy link
Member

XavierChanth commented Nov 25, 2024

OnboardService.onboard also needs better documentation, it has multiple responsibilities and they aren't clearly defined:

  • Automatic onboarding from keychain
  • Initial activation of atSign
  • Traditional onboard of a specific atSign?

@XavierChanth
Copy link
Member

XavierChanth commented Dec 9, 2024

My main goal is to obsolete this work, as with the introduction of the at_auth package, OnboardingService doesn't really have a good reason to exist. There's also a layer in at_client_mobile which is a wrapper around at_auth that also supports keychain.

The layer in at_onboarding_flutter which should exist is a service which adapts those layers in at_auth and at_client mobile to useful functions which directly map to the user flows for app onboarding, and provide useful progress updates (i.e. a progress stream) to the calling code rather than async results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants