-
Notifications
You must be signed in to change notification settings - Fork 9
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
Fix: postRender automatically setting blank component as completed #46
Conversation
Our requirements are that the blank component behaves according to the "Is this optional" setting. We use this component to determine if a user has viewed a page by placing a blank component at the top of each page with all other components set to optional. Therefore if you place a blank component at the top of the page and set it to NOT optional I would expect the menu of the course not to detect the page as complete until the user opens the page. This is how it currently works with the open source blank component but the Learning Pool one appears to act as optional despite the setting that has been set for "Is this optional" |
Here are some grabs showing a course with a single page that contains a blank component that is NOT optional. I have turned off the blank component appearing in the page level progress on the page. I can see when I look in the console that the course lesson status changes to "completed" when I open the page SCORM.data.set('cmi.core.lesson_status') value: completed |
Would you get the same outcome by adding That would retain the inviewability of the blank completion. |
Yes this is part of the difference that you are seeing @paulstevendev. The LearningPool AT will override these components and set them as optional always. We want to remove this when the new component functionality is added. |
@cahirodoherty-learningpool - the suggestion @oliverfoster has made sounds like a good compromise. If you did have a page where all the non blank components are set to optional then adding any blank components with a default setting of optional would result in page completion occur upon opening the course. However forcing the blank component to always act as optional is not an ideal solution for us so hopefully you can go with the suggestion by @oliverfoster |
Yeah that works for us. I've just pushed another commit |
Thanks Cahir - so just to clarify, we will still be able to set the blank component as not-optional and it will respect that? Hence if we set the blank component to not-optional, a page that contains this blank component will need to be opened before the page completes? |
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.
This makes eminent sense
Co-authored-by: Oliver Foster <[email protected]>
Co-authored-by: Oliver Foster <[email protected]>
Taking @paulstevendev as implicit +1 |
🎉 This PR is included in version 4.1.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Issue to resolve this raised here: #51 |
Fixes #45
Fix
Testing