Skip to content

Move a component - #14315

Merged
mushtaqak merged 16 commits into
masterfrom
mushtaq/move-component
Mar 14, 2017
Merged

Move a component#14315
mushtaqak merged 16 commits into
masterfrom
mushtaq/move-component

Conversation

@mushtaqak

@mushtaqak mushtaqak commented Jan 12, 2017

Copy link
Copy Markdown
Contributor

Description

This PR adds the ability to move a component to another location in the course.

This adds a move icon to a component. When move icon is clicked, the concise course outline is fetched and rendered via a modal dialog, which has the ability to navigate the course tree. The modal dialog describes which component is moved and tracks the current location (item ancestors). It only enables move button when a valid move operation can be made, otherwise it disabled.

When a component is moved, A mini notification is shown, reflecting the move operation is in progress, once operation is complete, successful confirmation message is shown to notify that the move operation is done. It also adds a link to the location component is moved. Furthermore, we also have the ability to undo the move operation which would put back the component to it original location.

The moved component is placed at the last index inside the new location.

TNL-5943

Sub PRs

#14204 : This PR adds the backend view to return tree for course outline and any given block
#14227 : This PR adds the backend view to move a component
#14254 : This PR adds move modal dialog
#14362 : This PR renders course outline and breadcrumbs on move modal
#14352 : This PR handles move and undo move front-end work
#14352 : This PR enables/ disables move button
#14457 : This PR restricts move operation for some cases and adds content experiments
#14364 : Test fixes
#14465 : This PR adds bokchoy tests
#14625 : This PR fixes some bugs introduced.
#14659 : This PR remove success banner on discard changes and adds logging and i18n support

@mushtaqak
mushtaqak force-pushed the mushtaq/move-component branch from 11f86e8 to e1d0af3 Compare January 26, 2017 12:00
@muzaffaryousaf

Copy link
Copy Markdown

jenkins run lettuce

@mushtaqak
mushtaqak force-pushed the mushtaq/move-component branch 2 times, most recently from 347ba8f to bcda015 Compare February 8, 2017 14:23
@mushtaqak
mushtaqak force-pushed the mushtaq/move-component branch from 7a2fed7 to a12ee2d Compare February 15, 2017 08:19
@mushtaqak
mushtaqak force-pushed the mushtaq/move-component branch from a12ee2d to e9b8e17 Compare March 1, 2017 14:28
@muzaffaryousaf

Copy link
Copy Markdown

@mushtaqak Can we add description to this PR and add links of all the sub-PRs that we've created for this feature with 1 liner to see what they have.

@muzaffaryousaf

Copy link
Copy Markdown

@catong We'll merge this feature tomorrow, i hope the doc is ready too.
@sstack22 FYI ^^

@catong

catong commented Mar 1, 2017

Copy link
Copy Markdown
Contributor

@muzaffaryousaf Yes, doc is ready to merge too.

Mushtaq Ali and others added 4 commits March 8, 2017 16:48
…omponent will now be the sibling of groups)

Fixed Move button is disabled when moving components inside conditional module

Fixed When navigating upward/backward, target parent is not set correct, resulting source to be moved in the previously selected parent
Add i18n to backend error messages in case they appear to end user
Remove success banner when trying to publish or discard changes on container page
Remove success banner on container state change
@muzaffaryousaf

Copy link
Copy Markdown

jenkins run lettuce

@muzaffaryousaf

Copy link
Copy Markdown

@sstack22 @catong @srpearce FYI, we're merging the feature branch into master.

@edx-pipeline-bot

Copy link
Copy Markdown
Contributor

EdX Release Notice: This PR has been deployed to the production environment.

@mushtaqak
mushtaqak deleted the mushtaq/move-component branch May 10, 2017 08:02
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

Successfully merging this pull request may close these issues.

5 participants