forked from openedx/frontend-app-authoring
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
12 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c63bc2f
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.
@rpenido This is intended behavior when creating a new library in mixed or v2 mode based on the description in the github issue. The new library created should be a v2 library, regardless if pressed on from v2 tab or the legacy tab. A v1 (legacy) library should be created only when in "v1 only" mode.
c63bc2f
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.
Hi @yusuf-musleh! Thank you for pointing this!
Reverted here: efe0bed
Edit: I found out why I changed it!
@bradenmacdonald
Could you clarify this requirement for us? Should clicking "+ New library" in mixed mode while in the legacy tab create a v1 or v2 library?
We have the following conflict here
and here
c63bc2f
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.
@rpenido @yusuf-musleh Sorry for the contradictory requirements. I think for now it's probably better to preserve the ability to create a v1 library even in mixed mode, so let's go with the second version for now: if mode is mixed and the legacy libraries tab is selected, redirect to the legacy studio page.