-
Notifications
You must be signed in to change notification settings - Fork 98
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
ShowCaseView on Interactive Book #170
Conversation
@manjotsidhu Implementation of showcase widget is done from side. I am currently working on the issues of the widget test. Please lemme know if there are any changes required. |
Thank you for your contributions @aman-singh7, Initial impressions of the code looks good. I will review and test it very soon. |
@manjotsidhu widget test ✔️ . |
@manjotsidhu could you give some info to fix the CI failing? 😅 |
The CI is not failing due to your changes. |
2c62d8e
to
1a249d4
Compare
@manjotsidhu can you now run the workflow? I have rebased the branch with master initially I just merged the master. |
Pull Request Test Coverage Report for Build 1610222365
💛 - Coveralls |
While testing, after showcasing next and previous buttons, it didn't show drawer showcase until I went to next/previous page. Is this intended ? |
The logic to trigger the Drawer Showcase is currently written inside |
I think I opened drawer button earlier so that might be the reason. |
I tested again, it triggered drawer showcase an reaching next pages. |
Screenrecorder-2021-11-26-19-39-01-11.mp4 |
I am updating the state of button clicked in |
*If not pressed implies if not pressed when showcased. |
Then the drawer showcase should be independent of toc being there or not. Drawer showcase is important initially. |
Cool.. I will seperate it from toc. |
Screenrecorder-2021-12-03-00-03-56-995.mp4@manjotsidhu I have updated the logic of showcasing. I have a doubt that the current implementation forces the user to click on the button when showcased otherwise it is going to showcase after every page changed. Do we need to force the user or not showcase the button which are previously clicked. |
We should not ideally force the user to click the button, if the user dismisses the showcase then it is safe to say that our showcasing is done and no need to show showcase again. |
3b79878
to
31afb98
Compare
@manjotsidhu can you now test the showcase? |
@manjotsidhu is the showcase working fine? |
Apologies for late reply, thanks for your contribution. I will test the showcase tonight but we will need to fix for iOS as well in order to merge. Would have been better if you have made a new PR for 2.8 since this PR's scope was showcase and we are also including fixes for 2.8. |
Ok, I will make a separate PR for 2.8 |
f8b1768
to
1647c87
Compare
c5fadd7
to
53454df
Compare
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.
✅ Tested and working perfectly on Android
✅ Implementation LGTM 👍
Fixes #105
Describe the changes you have made in this PR -
I have added the
ShowCaseView
package to showcase the button and toggles on the Interactive book and model for storing the state of the button pressed.Screenshots of the changes (If any) -
Screenrecorder-2021-11-21-17-17-24-212.mp4
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.