Sync changes from published unit

[sdaitzman]

Dependencies

Depends on #1710 and #1711. This story will require backend and frontend changes.

Spec

• Published unit changes cause units in course to receive the sync icon, just like components

In Scope

• Sync changes to unit in library that have been published to local instance in course
• Sync will "blow away all changes" to the course version of the unit, except for overrides (if any - the unit shouldn't have any changes because of Disallow edits to units in courses that are sourced from a library #1712)
  • Local text block overrides should be preserved. Local title overrides should be preserved. Local settings overrides should also be preserved. (Allowed/disallowed overrides #2182)
• Include test cases on the backend

Not in scope

• Bulk sync (should be integrated with that story)

[sdaitzman]

Sync operations that can be composed to write spec for this to result in intended behavior (via @kdmccormick at libraries delivery team sync):

1. Parent level fields (e.g. unit settings)
2. Child fields (e.g. component name and content)
3. Add missing children (e.g. new components in unit in library, or deleted local component that still exists in unit in library)
4. Remove stale children (e.g. local component that was added from same parent in library, but no longer exists there, or local component added locally)
   • (Not all extraneous ones; imported from other library or manually added intended override content should likely not be removed)
5. Reset order of synced children (e.g. component order within unit)

Some operations like Remove extraneous children will require specific logic to support intended behavior depending on stale/different-library links. We'll need to plan ahead to ensure this logic and expected behavior can be extended for sections/subsections eventually.

[sdaitzman]

Overrides to test against:

• Add children to parent in course from same library as parent
• Sync individual children in course, then sync parent

[jmakowski1123]

Minimal implementation

• Teak will not support local edits made to library units that are reused in a course. This will be an enhancement added for Ulma
• Library units in courses should be un-editable (grayed out?)
• When changes to the unit are made in the library and published, units in a course can be updated using the same syncing workflow as components
• Possibly out of scope for Teak - side-by-side comparison of changes if this is too complex

[bradenmacdonald]

@sdaitzman @jmakowski1123 Can we move the "minimal implementation" above into a new separate ticket, something like "Units from a library are read-only but syncable" ?

[pomegranited]

FYI @bradenmacdonald @jmakowski1123 This point was pulled into a separate ticket: #1712

Library units in courses should be un-editable (grayed out?)

[ChrisChV]

Hi @jmakowski1123 @sdaitzman @edschema, This is almost implemented in #1850. I'm attaching a video showing how the workflow is looking, so you can review. Thank you!

https://www.loom.com/share/70a14ccdb2ae487ea769be340d6ba845?sid=752e2e84-3553-4306-ad71-d21e40e4a682