-
Notifications
You must be signed in to change notification settings - Fork 19
Gigya Web SDK integration - setup Flutter Web entrypoint #69
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
base: main
Are you sure you want to change the base?
Gigya Web SDK integration - setup Flutter Web entrypoint #69
Conversation
| /// | ||
| /// The map is expected to have an `event` key, denoting the name of the event. | ||
| /// The map can have a `data` key, which is a [Map] that contains any data for the event. | ||
| factory ScreensetEvent.fromMap(Map<Object?, Object?> map) { |
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.
Adding this constructor makes the yield implementation a bit cleaner, since we can just rely on a tear-off and let dart format format the call-chain for us
| // The binary messenger sends things back as `dynamic`, | ||
| // but the events are actually a `Map<Object?, Object?>`. | ||
| // Cast using the `map()` Stream transformer. | ||
| yield* screenSetEvents |
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.
Combining a stream transformer + a tear-off makes this read better.
59e1ab7 to
a1febc3
Compare
d7f26f6 to
ade5a5c
Compare
|
@tal-mi As the work for the Biometrics service has been merged into main now, I have made the following changes to this pull request:
Once we get this pull request reviewed and merged, we can more easily split up the web implementation parts into smaller pieces. The PR's that I have opened for that, are currently drafts because most of their diffs are what is contained in this PR. |
This PR adds the web entrypoint for the example app.
The example web app won't run properly yet, since it currently lacks the most basic implementation of
initSdk(),logout(),isLoggedIn(). Implementing that is done in #45Part of #44
Changelog
Because we now have a web implementation part, I moved the method channel related stuff to its own folder
src/method_channelfolder (Android & iOS implementations)src/servicesfolderModel class related changes
SessionInfoclassfollowersCountinstead offollowersCountswhen converting a Profile from JSONdataparameter in theAccountclassBREAKING CHANGES
SessionInfoclass attributes are now nullable to account for differences between web and nativeAccount.socialProvidersis now a list of strings, which improves type safetyAccountclass have been refactored to becomeDateTime?instances.created,lastLogin,lastUpdated,oldestDataUpdated,registered,verifiedsignatureTimestamphas been updated to handleint,doubleandStringfor its parsingstartDateandendDateof aCertificationis now aDateTime?, instead of Stringtimestampfield has been removed from theLikeclass. Thetimeof aLikeis now a DateTimeConflictingAccountsclass has been renamed toConflictingAccount, the (web SDK) documentation uses singular for this object.