Unit cloning fails when the destination is a stand alone unit and has reference guides to be cloned #58686
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: When a unit is cloned and the destination is a standalone unit, the cloning script fails with a null reference exception at the step of cloning reference guides.
Root cause: The cloning step assumes that the destination unit is part of a unit group. As part of cloning reference guides, the course version is accessed through the unit group, which is null in case of standalone courses.
Fix: Leverage an already existing in-built function that has logic to determine course version for both stand alone and units that are part of unit groups.
Links
JIRA: https://codedotorg.atlassian.net/browse/TEACH-1109
Testing story
Added unit tests and drone
Deployment strategy
Regular DTP
Follow-up work
None
Privacy
N/A
Security
N/A
Caching
N/A
PR Checklist: