-
Notifications
You must be signed in to change notification settings - Fork 176
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
Completion duration updates #3777
Completion duration updates #3777
Conversation
…oes not include practice quiz fixes
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.
Approving so we can continue with testing.
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.
Some questions - not clear if they're about your implementation or the spec itself!
contentcuration/contentcuration/frontend/channelEdit/components/edit/ActivityDuration.vue
Outdated
Show resolved
Hide resolved
contentcuration/contentcuration/frontend/channelEdit/components/edit/CompletionOptions.vue
Outdated
Show resolved
Hide resolved
@@ -324,6 +323,13 @@ | |||
model: CompletionCriteriaModels.REFERENCE, | |||
threshold: null, | |||
}; | |||
} else if (value === CompletionDropdownMap.completeDuration) { | |||
// set to '1' as the minimum here, due to validation rules requiring > 0 |
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.
Not sure I understand why we're setting a default here - feels like if there is no value, we need to let the user set it.
contentcuration/contentcuration/frontend/channelEdit/components/edit/CompletionOptions.vue
Outdated
Show resolved
Hide resolved
Merging this for now for further QA testing. There is still an extant issue with duration setting for exact duration, but we can fix that in follow up. |
@marcellamaki Here are the issues that I was able to identify:
|
Thank you @pcenov! I will look into all of these |
Summary
Description of the change(s) you made
These changes are to ensure that data is persisted correctly in the front and back end, and there are no "invisible" validations that cause data to not be saved as expected.
edited: This has been implemented and checked for: video, audio, document, html5, and practice quizzes
Manual verification steps performed
For each file type listed above
Does this introduce any tech-debt items?
Tests still need to be finalized for this PR. It has been opened just for the sake of timely manual QA.
Reviewer guidance
How can a reviewer test these changes?
See manual verification steps above.
Are there any risky areas that deserve extra testing?
Any notable problem areas from open issues, especially:
across all relevant content types.
Comments
When testing on the dev server, the audio and video default files that are generated for engineers (
yarn run devsetup
) are both 00:00 long. This does cause an error, as for audio and video files, there is a required minimum in the validation to be > 0. I am not sure if these files are in the usual manual QA workflow, but please do note that mp3 or mp4 files that are 0 seconds long will fail to save. I will check in with @rtibbles to see if we should handle this in a different way, or if it too small of an edge case to consider.Contributor's Checklist
PR process:
CHANGELOG
label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later timedocs
label has been added if this introduces a change that needs to be updated in the user docs?requirements.txt
files also included in this PRStudio-specifc:
notranslate
class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)pages
,components
, andlayouts
directories as described in the docsTesting:
Reviewer's Checklist
This section is for reviewers to fill out.
yarn
andpip
)