Skip to content
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

Bug: Draft version of component is copied on course #241

Closed
ChrisChV opened this issue Nov 20, 2024 · 2 comments
Closed

Bug: Draft version of component is copied on course #241

ChrisChV opened this issue Nov 20, 2024 · 2 comments

Comments

@ChrisChV
Copy link

If a user wants to add a library component using the library component picker, can only pick the published versions of the components. But when copying a component from the clipboard and pasting it into a course, the draft version is pasted.

Steps to reproduce:

  1. Create a library in the Authoring MFE.
  2. Create a component in your library with a name like "This is a test".
  3. Publish the library.
  4. Edit the component in your library, like "Edited component".
  5. Copy the component to the clipboard.
  6. Go to a course unit and paste the component.
  7. The draft version of the component is pasted. Expected behavior: The published version of the component is pasted.
@ChrisChV
Copy link
Author

CC @bradenmacdonald @jmakowski1123

@ChrisChV ChrisChV changed the title Bug: Published version is not copied on course Bug: Published version of component is not copied on course Nov 20, 2024
@ChrisChV ChrisChV changed the title Bug: Published version of component is not copied on course Bug: Draft version of component is copied on course Nov 20, 2024
@bradenmacdonald
Copy link
Contributor

@ChrisChV Thanks for carefully testing and reporting this. However, this is actually expected behavior. When you copy something, you copy exactly what you see, which may be a draft. If you copied something that said "A" and then you pasted it and it suddenly said "B", that would be confusing. (Principle of Least Surprise)

We actually developed and tested this scenario carefully, so that for example when you copy version 5 (draft) and then go back to the library and publish it, nothing will show as changed in the course. But when you publish a new version 6, then the course will show that an update is now available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants