-
Notifications
You must be signed in to change notification settings - Fork 11
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
ALTAPPS-1030: [Shared, iOS] Fill blanks problem onboarding modal #740
ALTAPPS-1030: [Shared, iOS] Fill blanks problem onboarding modal #740
Conversation
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.
It's nice that now we have common approach to new onboarding types 👍
fun isParsonsOnboardingShown(): Boolean | ||
fun setParsonsOnboardingShown(isShown: Boolean) | ||
|
||
fun isFillBlanksInputModeOnboardingShown(): Boolean | ||
fun setFillBlanksInputModeOnboardingShown(isShown: Boolean) | ||
fun isFillBlanksSelectModeOnboardingShown(): Boolean | ||
fun setFillBlanksSelectModeOnboardingShown(isShown: Boolean) |
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.
Maybe here it would be better to use problem type to have only one method for caching. WIth adding new problem types onboardings it would be easier to support
* { | ||
* "route": "/learn/step/1", | ||
* "action": "hidden", | ||
* "part": "parsons_problem_onboarding_modal", |
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.
in such comments we usually add all possible values like parsons_problem_onboarding_modal | fill_blanks_problem_onboarding_modal
YouTrack Issues:
#ALTAPPS-1030
Checklist
Before Code Review:
Description