feat: added soft delete functionality by Alam-2U · Pull Request #6 · edx/frontend-app-discussions

Alam-2U · 2025-11-03T11:26:10Z

Description

Implements soft delete functionality for discussion threads, responses, and comments using the is_deleted flag instead of permanently deleting records.
This enables safe deletion and restoration of discussion content while preserving existing data.

Changes Made

Added soft delete and restore functionality for threads, responses, and comments.
Introduced support to view deleted content in the Learner tab using a new Active / Deleted filter.
Implemented restore actions for deleted threads, responses, and comments.
Added deleted count tracking and support for sorting by deleted count in the Learner tab.
Implemented bulk delete and bulk restore actions for discussion content.
Ensured nested responses and comments are handled correctly during delete and restore operations.
Added API support to fetch deleted content for moderation workflows.

Note:
Features listed above (except soft delete itself) are available only to Staff, Admins, Moderators, and TAs.

JIRA Tickets

COSMO2-742 – Link
COSMO2-769 – Link
COSMO2-783 – Link

Related Pull Requests

Copilot

Pull request overview

This PR implements comprehensive soft delete functionality for discussion threads, responses, and comments, allowing content to be marked as deleted rather than permanently removed from the database. The implementation includes UI indicators for deleted content, restore capabilities, and bulk operations for managing user contributions.

Key Changes:

Added soft delete and restore actions with confirmation dialogs for threads, responses, and comments
Implemented filtering between active and deleted content with dedicated views for moderators/staff
Added bulk delete and restore operations for user posts at course and organization levels

Reviewed changes

Copilot reviewed 47 out of 48 changed files in this pull request and generated 26 comments.

Show a summary per file

File	Description
`src/index.scss`	Added styling for deleted content indicators, learner message badges, and submenu containers
`src/discussions/utils.js`	Extended action permissions to support restore operations and disabled actions for deleted items
`src/discussions/posts/post/messages.js`	Added internationalized messages for delete/restore confirmations and deleted content badges
`src/discussions/posts/post/PostLink.jsx`	Enhanced post links to display deleted state with visual indicators and handle response/comment navigation
`src/discussions/posts/post/Post.jsx`	Integrated restore confirmation dialogs and deleted-by attribution display
`src/discussions/posts/post-filter-bar/messages.js`	Added filter labels for active vs deleted content status
`src/discussions/posts/index.js`	Exported PostLink component for reuse in learner views
`src/discussions/posts/data/thunks.js`	Implemented thread restore thunk and filter logic for active/deleted content
`src/discussions/posts/data/slices.js`	Changed default filter to active content and added deleted view state management
`src/discussions/posts/data/selectors.js`	Added selector for deleted view state
`src/discussions/posts/data/api.js`	Created API endpoint for restoring deleted threads
`src/discussions/posts/data/__factories__/threads.factory.js`	Added is_deleted field to thread factory for testing
`src/discussions/posts/PostsView.test.jsx`	Updated tests to reflect new default "active" filter
`src/discussions/posts/NoResults.jsx`	Fixed optional chaining for learner state access
`src/discussions/post-comments/messages.js`	Added restore confirmation messages for responses and comments
`src/discussions/post-comments/data/thunks.js`	Extended fetch operations to support showDeleted parameter and added restore thunk
`src/discussions/post-comments/data/hooks.js`	Implemented deleted content visibility logic based on filter state
`src/discussions/post-comments/data/api.js`	Added showDeleted parameter to API calls and restore comment endpoint
`src/discussions/post-comments/data/__factories__/comments.factory.js`	Added is_deleted field to comment factory
`src/discussions/post-comments/comments/comment/Reply.jsx`	Integrated restore functionality and deleted-by attribution for replies
`src/discussions/post-comments/comments/comment/CommentHeader.jsx`	Added flex-wrap to header for better responsive layout
`src/discussions/post-comments/comments/comment/Comment.jsx`	Implemented restore logic and deleted state handling for comments and responses
`src/discussions/post-comments/PostCommentsView.test.jsx`	Updated test expectations for show_deleted parameter
`src/discussions/messages.js`	Added restore action message and bulk operation labels
`src/discussions/learners/utils.js`	Created learner actions menu with nested delete/restore submenus
`src/discussions/learners/messages.js`	Added messages for deleted activity stats and restore operations
`src/discussions/learners/learner/proptypes.js`	Extended learner shape with deleted content counts
`src/discussions/learners/learner/LearnerFooter.jsx`	Added deleted activity indicator for staff/moderators
`src/discussions/learners/learner/LearnerFilterBar.jsx`	Added deleted activity sorting option
`src/discussions/learners/learner/LearnerCard.jsx`	Passed deleted stats to footer component
`src/discussions/learners/learner-post-filter-bar/LearnerPostFilterBar.test.jsx`	Updated tests for new content status filter radiogroup
`src/discussions/learners/learner-post-filter-bar/LearnerPostFilterBar.jsx`	Added content status filter for active/deleted distinction
`src/discussions/learners/data/thunks.js`	Implemented deleted content fetching and restore operations
`src/discussions/learners/data/slices.js`	Added restore action reducers and merged filter updates
`src/discussions/learners/data/redux.test.jsx`	Added test assertion for default contentStatus
`src/discussions/learners/data/api.js`	Created APIs for bulk restore and fetching deleted content
`src/discussions/learners/LearnerPostsView.test.jsx`	Updated tests to handle submenu interactions
`src/discussions/learners/LearnerPostsView.jsx`	Integrated restore confirmations and post refresh logic
`src/discussions/learners/LearnerActionsDropdown.test.jsx`	Added submenu hover interactions to tests
`src/discussions/learners/LearnerActionsDropdown.jsx`	Implemented nested submenu with portal rendering for delete/restore actions
`src/discussions/data/thunks.js`	Added performRestoreThread thunk
`src/discussions/data/selectors.js`	Updated filter logic to treat ACTIVE status as unfiltered
`src/discussions/data/constants.js`	Added THREAD_FILTER_TYPES constants
`src/discussions/common/HoverCard.jsx`	Disabled interactive actions for deleted content
`src/discussions/common/ActionsDropdown.jsx`	Added disabled state handling for action items
`src/data/constants.js`	Added RESTORE action and ACTIVE/DELETED status filter constants
`src/components/FilterBar.jsx`	Enhanced filter bar to support separated filter sections
`src/assets/undelete.svg`	Added restore/undelete icon SVG

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/discussions/data/selectors.js

Copilot · 2025-12-18T09:38:22Z

src/discussions/learners/learner-post-filter-bar/LearnerPostFilterBar.jsx


 import FilterBar from '../../../components/FilterBar';
-import { PostsStatusFilter, ThreadType } from '../../../data/constants';
+// import { PostsStatusFilter, ThreadType } from '../../../data/constants';


The commented-out import statement should be removed rather than commented. If these imports are needed, they should be active; if not, remove them entirely. Commented code creates confusion and clutter in the codebase.

Suggested change

// import { PostsStatusFilter, ThreadType } from '../../../data/constants';

src/index.scss

Copilot · 2025-12-18T09:38:23Z

src/discussions/utils.js

+  ).map(action => ({
+    ...action,
+    // For deleted items, disable all actions except 'copy-link' and 'restore'
+    disabled: content.isDeleted && action.id !== 'copy-link' && action.id !== 'restore',
+  })), [content]);


The action filtering logic now adds a disabled property based on isDeleted state. However, this mutates the action objects during rendering which could cause issues with memoization. Consider moving this logic into the checkPermissions or checkConditions functions instead, or creating new action objects rather than spreading and modifying existing ones.

Copilot · 2025-12-18T09:38:23Z

src/discussions/posts/post/Post.jsx

+      if (result.success) {
+        window.location.reload();


After restoring a thread, the code calls window.location.reload() which causes a full page refresh. This is not ideal for user experience as it loses the current state and causes a jarring transition. Consider using Redux state updates to refresh just the thread data instead of reloading the entire page.

Copilot · 2025-12-18T09:38:30Z

src/discussions/posts/NoResults.jsx

+  const learnersFilter = useSelector(({ learners }) => learners?.usernameSearch);
  const isFiltered = postsFiltered || (topicsFilter !== '')
-    || (learnersFilter !== null) || (inContextTopicsFilter !== '');
+    || (learnersFilter) || (inContextTopicsFilter !== '');


The optional chaining learners?.usernameSearch and learners?.postFilter suggests that the learners state might be undefined in some cases. However, this defensive programming is inconsistent - other parts of the codebase access state.learners directly without null checks. Consider either making the learners reducer always defined or consistently use optional chaining throughout.

src/discussions/post-comments/data/hooks.js

Copilot · 2025-12-18T09:38:31Z

src/discussions/learners/data/thunks.js

+        const { getDeletedContent } = await import('./api');
+        data = await getDeletedContent(courseId, {
+          author,
+          page,
+          pageSize: 10,
+        });
+      } else {
+        // Use regular learner posts endpoint for active content
+        const { getUserPosts } = await import('./api');


The code dynamically imports API functions inside the thunk (const { getDeletedContent } = await import('./api')). While lazy loading can help with bundle size, this creates inconsistency since other API calls in the same file use static imports. Either use dynamic imports consistently or use static imports for all APIs in this file to avoid confusion and ensure predictable loading behavior.

src/discussions/learners/data/api.js

src/discussions/learners/LearnerActionsDropdown.jsx

Copilot

Pull request overview

Copilot reviewed 47 out of 48 changed files in this pull request and generated 9 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/discussions/posts/post/Post.jsx

Copilot · 2025-12-18T11:19:02Z

src/discussions/learners/learner-post-filter-bar/LearnerPostFilterBar.jsx


 import FilterBar from '../../../components/FilterBar';
-import { PostsStatusFilter, ThreadType } from '../../../data/constants';
+// import { PostsStatusFilter, ThreadType } from '../../../data/constants';


Commented out import statement should be removed. The commented import is replaced by the new imports above it, so this line should be deleted to keep the code clean.

Suggested change

// import { PostsStatusFilter, ThreadType } from '../../../data/constants';

Copilot · 2025-12-18T11:19:02Z

src/discussions/learners/learner-post-filter-bar/LearnerPostFilterBar.jsx

    },
    {
-      name: 'status',
+      name: 'status', // secondary status


The inline comment 'secondary status' is potentially misleading. This comment suggests there's a distinction between primary and secondary status filters, but this isn't clearly documented elsewhere. Consider either adding more comprehensive documentation or removing the comment if it doesn't add clarity.

Copilot · 2025-12-18T11:19:02Z

src/discussions/learners/data/thunks.js

+      if (filters.contentStatus === PostsStatusFilter.DELETED) {
+        const { getDeletedContent } = await import('./api');
+        data = await getDeletedContent(courseId, {
+          author,
+          page,
+          pageSize: 10,
+        });


Missing error handling for the dynamic import. If the import of 'getDeletedContent' fails, it will throw an unhandled error. Consider wrapping the import in a try-catch block or handling the error appropriately.

src/discussions/posts/post/PostLink.jsx

Copilot · 2025-12-18T11:19:03Z

src/discussions/posts/post/PostLink.jsx

+  const displayTitle = (type === 'response' || type === 'comment') && threadTitle ? threadTitle : title;
+
+  // For comments/responses, navigate to the parent thread instead of the comment itself
+  const navigationPostId = (type === 'response' || type === 'comment') && commentThreadId ? commentThreadId : postId;


The navigationPostId calculation could result in undefined if both commentThreadId and postId are falsy. This could lead to navigation errors or broken links. Add validation to ensure a valid post ID is always used.

src/discussions/post-comments/comments/comment/Comment.jsx

Copilot

Pull request overview

Copilot reviewed 46 out of 47 changed files in this pull request and generated 16 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

src/discussions/learners/LearnerActionsDropdown.jsx

Copilot · 2025-12-19T15:25:17Z

src/discussions/common/HoverCard.jsx

+            onClick={() => !isDeleted && handleResponseCommentButton()}
+            disabled={isClosed || isDeleted}
+            style={{ lineHeight: '20px', ...(isDeleted ? { opacity: 0.3, cursor: 'not-allowed' } : {}) }}


The onClick handler on line 54 checks !isDeleted before calling the function, but the button is also disabled when isDeleted is true (line 55). This creates redundant protection. Either the disabled state is sufficient, or if you need the onClick check for some reason, document why both are necessary.

Copilot · 2025-12-19T15:25:18Z

src/discussions/utils.js

 */
 export function checkPermissions(content, action) {
-  if (content.editableFields.includes(action)) {
+  if (content.editableFields && content.editableFields.includes(action)) {


Defensive check added for editableFields is good, but this suggests content.editableFields might be undefined or null. Consider whether this is expected behavior or if the API response should be normalized to always include editableFields as an empty array when not present.

src/discussions/posts/post/PostLink.jsx

src/discussions/posts/data/api.js

Copilot · 2025-12-19T15:25:20Z

src/discussions/learners/learner-post-filter-bar/LearnerPostFilterBar.jsx

+  }
+
  if (userHasModerationPrivileges || userIsGroupTa) {
+    // Add reported filter only for group TA and moderators


The comment says 'Add reported filter only for group TA and moderators' but the condition checks for both userHasModerationPrivileges OR userIsGroupTa. This means moderators AND group TAs will see this filter, not just group TAs and moderators as a combined role. The comment should be clarified to match the actual logic.

Copilot · 2025-12-19T15:25:20Z

src/discussions/learners/data/api.js

+  contentType,
+} = {}) {
+  const params = snakeCaseObject({
+    authorId: author, // The backend expects author_id


The API parameter name has been changed from 'authorId' (with snake_case conversion to 'author_id') on line 153 to use 'authorId' which will be converted to 'author_id' by snakeCaseObject. However, the comment on line 153 says 'The backend expects author_id'. Verify that the backend actually accepts this parameter name, as the getUserPosts function uses 'username' (line 81) for the author parameter.

Copilot · 2025-12-19T15:25:20Z

src/discussions/learners/LearnerActionsDropdown.jsx

+  useEffect(() => () => {
+    if (isOpen) {
+      close();
+      setTarget(null);
+      setActiveSubmenu(null);
+    }


The cleanup effect on lines 49-55 will run on every render because it doesn't have a dependency array. This means it sets up a new cleanup function on every render, which is inefficient. Add an empty dependency array [] to ensure this cleanup only runs on unmount.

Suggested change

useEffect(() => () => {

if (isOpen) {

close();

setTarget(null);

setActiveSubmenu(null);

}

useEffect(() => {

return () => {

if (isOpen) {

close();

setTarget(null);

setActiveSubmenu(null);

}

};

Copilot · 2025-12-19T15:25:20Z

src/discussions/post-comments/data/api.js

+ * @returns {Promise<{}>}
+ */
+export const restoreComment = async (commentId, courseId) => {
+  const url = `${getConfig().LMS_BASE_URL}/api/discussion/v1/restore_content`;


The API function restoreComment uses a hardcoded endpoint '/api/discussion/v1/restore_content'. This is the same endpoint as used in threads (src/discussions/posts/data/api.js line 227). Consider extracting this to a shared constant or helper function to avoid duplication and ensure consistency.

Copilot · 2025-12-19T15:25:21Z

src/discussions/posts/post/PostLink.jsx

                <span className={classNames(
                  'font-weight-500 text-primary-500 font-style align-bottom mr-1',
                  { 'font-weight-bolder': !read },
+                  { 'text-decoration-line-through': isDeleted }, // Line-through for deleted threads


The inline comment on line 138 says 'Line-through for deleted threads' but this style is applied to all deleted content (threads, responses, and comments based on the displayTitle logic). The comment should be updated to reflect this broader scope or be more generic.

Copilot

Pull request overview

Copilot reviewed 46 out of 47 changed files in this pull request and generated 21 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-12-29T11:31:53Z

src/index.scss

+.learner-submenu-container {
+  position: absolute;
+  left: 100%;
+  top: 0;
+  min-width: 300px;
+  max-width: 360px;
+  z-index: 9999;
+  box-shadow: 0 2px 8px rgba(0, 0, 0, 0.15);
+  border: 1px solid var(--pgn-color-light-400);
+  overflow: visible;
+}


There is duplicate CSS for .learner-submenu-container defined at both lines 603-610 and lines 897-907. The definitions have slightly different properties (e.g., different min-width values: 280px vs 300px, and different max-width values: 320px vs 360px). This duplication should be consolidated into a single definition to avoid confusion and potential styling conflicts.

Copilot · 2025-12-29T11:31:54Z

src/discussions/utils.js

+  const isActionDisabled = useCallback((actionId, isDeleted) => (
+    // For deleted items, disable all actions except 'copy-link' and 'restore'
+    isDeleted && actionId !== 'copy-link' && actionId !== 'restore'
+  ), []);


In the isActionDisabled callback, the logic disables all actions except 'copy-link' and 'restore' for deleted items. However, this function is defined within useActions which is called with content as a dependency. The function should also include content in its dependency array to ensure it updates when the content changes. Currently, the empty dependency array [] means this callback never updates even if the content's deleted state changes.

Copilot · 2025-12-29T11:31:54Z

src/discussions/posts/post/Post.jsx

+  const handleRestoreConfirmation = useCallback(async () => {
+    try {
+      const { performRestoreThread } = await import('../data/thunks');
+      const result = await dispatch(performRestoreThread(postId, courseId));
+      // Check if restore failed and log the error
+      if (result && !result.success) {
+        logError(`Failed to restore thread: ${result.error || 'Unknown error'}`);
+      }
+    } catch (error) {
+      logError(error);
+    }
+    hideRestoreConfirmation();
+  }, [postId, courseId, dispatch, hideRestoreConfirmation]);


The restore handler on lines 116-128 checks if (result && !result.success) and logs an error, but it doesn't provide any user feedback about the failure. Users should be notified when a restore operation fails so they understand why the content wasn't restored. Consider adding a toast notification or error message display for failed restore operations.

Copilot · 2025-12-29T11:31:54Z

src/discussions/common/ActionsDropdown.jsx

+              if (!action.disabled) {
+                handleActions(action.action);
+              }


The click handler on lines 80-83 prevents the action from executing if action.disabled is true, but this check is redundant since the button already has disabled={action.disabled} on line 87. The disabled attribute on the button should already prevent click events from firing. This redundant check adds unnecessary complexity.

Suggested change

if (!action.disabled) {

handleActions(action.action);

}

handleActions(action.action);

Copilot · 2025-12-29T11:31:54Z

src/discussions/posts/data/thunks.js

+export function performRestoreThread(threadId, courseId) {
+  return async (dispatch) => {
+    try {
+      const { restoreThread } = await import('./api');
+      const data = await restoreThread(threadId, courseId);
+      // Update the thread in Redux state to reflect the restore
+      dispatch(updateThreadSuccess(camelCaseObject(data)));
+      return { success: true };
+    } catch (error) {
+      logError(error);
+      return { success: false, error: error.message };
+    }
+  };
+}


The performRestoreThread thunk on lines 327-340 returns an object with { success: true } or { success: false, error: error.message }. However, Redux thunks typically don't need to return success/failure indicators - they should dispatch actions that update the state accordingly. The calling code then checks this return value, which is an anti-pattern. Consider having the thunk dispatch success/failure actions and let components observe state changes instead of checking return values.

Copilot · 2025-12-29T11:31:58Z

src/discussions/post-comments/comments/comment/Reply.jsx

+      }
+    } catch (error) {
+      logError(error);
+    }
+    hideRestoreConfirmation();
+  }, [id, courseId, threadId, dispatch, hideRestoreConfirmation]);


The handleRestoreConfirmation function on lines 86-96 handles errors by logging them but doesn't provide user feedback when an error occurs. Similar to the thread restore operation, users should be notified if restoring a comment fails. Consider adding error notification to inform users of failures.

Suggested change

}

} catch (error) {

logError(error);

}

hideRestoreConfirmation();

}, [id, courseId, threadId, dispatch, hideRestoreConfirmation]);

} else {

window.alert(intl.formatMessage({

id: 'discussions.comment.restore.error',

defaultMessage: 'There was a problem restoring this comment. Please try again.',

}));

}

} catch (error) {

logError(error);

window.alert(intl.formatMessage({

id: 'discussions.comment.restore.error',

defaultMessage: 'There was a problem restoring this comment. Please try again.',

}));

}

hideRestoreConfirmation();

}, [id, courseId, threadId, dispatch, hideRestoreConfirmation, intl]);

Copilot · 2025-12-29T11:31:58Z

src/discussions/post-comments/comments/comment/Comment.jsx

+        await dispatch(fetchThread(threadId, courseId));
+      }
+    } catch (error) {
+      logError(error);


Similar to other restore operations, the handleRestoreConfirmation function on lines 142-154 logs errors but doesn't notify the user when a restore operation fails. Users need feedback about failed operations to understand what went wrong and potentially retry or take alternative action.

Suggested change

logError(error);

logError(error);

window.alert('Unable to restore this comment. Please try again.');

Copilot · 2025-12-29T11:31:58Z

src/discussions/posts/data/slices.js

    postStatus: RequestStatus.SUCCESSFUL,
    filters: {
-      status: PostsStatusFilter.ALL,
+      status: PostsStatusFilter.ACTIVE,


The default status filter has been changed from PostsStatusFilter.ALL to PostsStatusFilter.ACTIVE on line 49. This is a significant behavior change that will affect all users - they will now only see active (non-deleted) posts by default. While this is likely intentional for the soft delete feature, this change should be clearly documented in the PR description as it changes the default user experience. Additionally, consider if there should be any migration or notification to existing users about this change.

Copilot · 2025-12-29T11:31:59Z

src/discussions/post-comments/data/thunks.js

+export function performRestoreComment(commentId, courseId) {
+  return async () => {
+    try {
+      const { restoreComment } = await import('./api');
+      await restoreComment(commentId, courseId);
+      return { success: true };
+    } catch (error) {
+      logError(error);
+      return { success: false, error: error.message };
+    }
+  };
+}


The performRestoreComment thunk on lines 194-205 follows the same anti-pattern as the thread restore thunk, returning success/failure objects instead of relying on Redux state management. Additionally, this thunk doesn't dispatch any actions to update the Redux state after successfully restoring a comment. This means the UI won't reflect the restored state until the parent component manually refreshes (as seen with the fetchThread call in the component). Consider dispatching an action to update the comment state directly.

Copilot · 2025-12-29T11:31:59Z

src/discussions/learners/LearnerActionsDropdown.jsx

+                  {activeSubmenu === item.id && (
+                    <div className="bg-white learner-submenu-container">
+                      {item.submenu.map(subItem => (
+                        <Dropdown.Item
+                          key={subItem.id}
+                          as={Button}
+                          variant="tertiary"
+                          size="inline"
+                          onClick={() => handleActions(subItem.action)}
+                          className="d-flex justify-content-start actions-dropdown-item"
+                          data-testid={subItem.id}
+                        >
+                          <span className="font-weight-normal">
+                            {subItem.label}
+                          </span>
+                        </Dropdown.Item>
+                      ))}
+                    </div>
+                  )}


The submenu implementation on lines 104-122 shows the submenu when activeSubmenu === item.id. However, the submenu is positioned absolutely (position: absolute in CSS) and uses left: 100% to position it to the right of the parent menu. This positioning approach could cause the submenu to overflow off-screen on smaller viewports or when the dropdown is near the right edge of the window. Consider adding logic to detect available space and flip the submenu to the left side when necessary.

santhosh-apphelix-2u

As discussed, I am approving this PR for now, but it will require refactoring as discussed.

This reverts commit 9dc3367.

Alam-2U force-pushed the ealam/COMSO2-742 branch 5 times, most recently from 1d1ac54 to 8711640 Compare November 6, 2025 06:04

Alam-2U force-pushed the ealam/COMSO2-742 branch from d997095 to fd9406c Compare November 24, 2025 09:29

Alam-2U marked this pull request as ready for review December 18, 2025 09:22

Copilot AI review requested due to automatic review settings December 18, 2025 09:22

Copilot started reviewing on behalf of Alam-2U December 18, 2025 09:22 View session

Copilot AI reviewed Dec 18, 2025

View reviewed changes

Alam-2U force-pushed the ealam/COMSO2-742 branch from 94b4ad6 to f296e1e Compare December 18, 2025 10:55

Copilot AI review requested due to automatic review settings December 18, 2025 11:09

Copilot started reviewing on behalf of Alam-2U December 18, 2025 11:09 View session

Alam-2U force-pushed the ealam/COMSO2-742 branch from 5adc134 to 2f2eff9 Compare December 18, 2025 11:14

Copilot AI reviewed Dec 18, 2025

View reviewed changes

jcapphelix mentioned this pull request Dec 18, 2025

feat: soft delete edx/edx-platform#37

Merged

Alam-2U requested a review from jcapphelix December 18, 2025 17:11

Alam-2U force-pushed the ealam/COMSO2-742 branch from 2f2eff9 to 94b4ad6 Compare December 19, 2025 09:25

jcapphelix mentioned this pull request Dec 19, 2025

feat: soft delete edx/forum#4

Merged

4 tasks

Copilot AI review requested due to automatic review settings December 19, 2025 15:19

Copilot started reviewing on behalf of Alam-2U December 19, 2025 15:19 View session

Copilot AI reviewed Dec 19, 2025

View reviewed changes

feat: added soft delete functionality

b5256de

Alam-2U force-pushed the ealam/COMSO2-742 branch from ce670c9 to b5256de Compare December 29, 2025 10:31

Alam-2U added 2 commits December 29, 2025 16:04

Merge branch 'master' into ealam/COMSO2-742

b5f6016

fix: copilot comments

2037571

Copilot AI review requested due to automatic review settings December 29, 2025 11:26

Copilot started reviewing on behalf of Alam-2U December 29, 2025 11:26 View session

Copilot AI reviewed Dec 29, 2025

View reviewed changes

Alam-2U requested a review from santhosh-apphelix-2u January 6, 2026 07:28

santhosh-apphelix-2u approved these changes Jan 6, 2026

View reviewed changes

Alam-2U merged commit 9dc3367 into master Jan 6, 2026
9 checks passed

jcapphelix added a commit that referenced this pull request Jan 7, 2026

Revert "feat: added soft delete functionality (#6)"

3f0a8c1

This reverts commit 9dc3367.

jcapphelix mentioned this pull request Jan 7, 2026

revert "feat: added soft delete functionality" #13

Merged

Alam-2U pushed a commit that referenced this pull request Jan 7, 2026

Revert "feat: added soft delete functionality (#6)" (#13)

71d4584

This reverts commit 9dc3367.

This was referenced Jan 12, 2026

feat: added soft delete functionality edx/edx-platform#83

Merged

feat: added soft delete functionality edx/forum#10

Merged

	logError(error);
	logError(error);
	window.alert('Unable to restore this comment. Please try again.');

Conversation

Alam-2U commented Nov 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Changes Made

JIRA Tickets

Related Pull Requests

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI Dec 18, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Copilot AI Dec 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 19, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Copilot AI Dec 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Dec 19, 2025

Choose a reason for hiding this comment

Uh oh!

Alam-2U commented Nov 3, 2025 •

edited

Loading