edx-platform

Files

Taimoor Ahmed 4c051378d0 feat!: remove last calls to cs_comments_service (#37376 )

This removes the last remaining code that called out to the
cs_comments_service. All forums backend logic now uses the v2 API from
the forum repo (https://github.com/openedx/forum). This does NOT remove
MongoDB support.

This also implements the endpoint to retrieve all comments for a user
using the new forum backend. This is not actually called from any known
frontend code, but it has not been formally deprecated as an endpoint,
and therefore needs to be supported.

As part of the cleanup, the ENABLE_FORUM_V2 course waffle flag has also
been removed, along with all remaining switching logic that used to
route between the Python API in the forum repo and service calls to the
cs_comments_service Ruby service.

Other endpoints affected (switching logic removed):

* get course commentable counts
* get/update course user stats
* update comment/thread/user
* delete thread (implementation moved to forum repo)
* follow
* retire user

This is part of the following overall DEPR ticket:
  https://github.com/openedx/cs_comments_service/issues/437

2025-10-08 11:36:52 -04:00

config

fix: updated captcha api to use enterprise assessment (#37079 )

2025-08-03 21:27:12 +00:00

django_comment_client

feat!: remove last calls to cs_comments_service (#37376 )

2025-10-08 11:36:52 -04:00

management

feat: Add management command for updating discussion user stats for all users in a course (#29973 )

2022-04-13 19:09:50 +05:00

notification_prefs

chore: remove some usages of six (Python2 compat) (#32554 )

2023-07-17 12:18:43 -07:00

rest_api

feat!: remove last calls to cs_comments_service (#37376 )

2025-10-08 11:36:52 -04:00

settings

refactor: flatten FEATURES dictionary with backward compatible proxy

2025-09-09 14:11:39 -06:00

signals

feat: Add notify all learners option for discussion post (#36922 )

2025-06-27 15:25:22 +05:00

static/discussion

Revert "fix: all auto fixable eslint issues (#31900 )" (#32203 )

2023-05-09 13:53:54 +05:00

templates/discussion

chore: [FC-0047] change push notifications texts

2024-09-06 17:45:23 +03:00

tests

feat!: remove last calls to cs_comments_service (#37376 )

2025-10-08 11:36:52 -04:00

__init__.py

Discssions as a plugin

2018-02-23 09:23:53 -05:00

apps.py

fix: fixed unregistered task in new thread notification (#33223 )

2023-09-12 14:02:31 +05:00

exceptions.py

BOM-2278 : Pylint amnesty in discussion, dashboard (#26275 )

2021-02-03 18:15:14 +05:00

plugins.py

feat: hide discussion tab when disabled (#32195 )

2023-05-16 05:17:06 +05:00

rate_limit.py

feat: added configurable ratelimit feature in discussions (#37094 )

2025-07-31 17:35:10 +05:00

README.rst

Remove notifier_api app DEPR-111 (#25464 )

2020-10-29 11:17:23 -04:00

tasks.py

fix: enable pylint warnings (#36196 )

2025-02-03 14:18:11 +05:00

toggles_utils.py

fix: removed enable_discussion_mfe from email content (#34061 )

2024-01-16 12:12:55 +05:00

toggles.py

feat: added configurable ratelimit feature in discussions (#37094 )

2025-07-31 17:35:10 +05:00

urls.py

BOM-2781: Django codemods on LMS (2) (#28852 )

2021-11-11 17:52:57 +05:00

views.py

fix: legacy forum issues (#36470 )

2025-04-07 19:04:14 +05:00

README.rst

Status: Maintenance

Responsibilities
================
The Discussion app powers the Open edX forums experience.

Direction: Move and Extract
===========================
Discussions related functionality is scattered across a number of places and should be better consolidated. Today we have:

* ``lms/djangoapps/discussion``
* ``openedx/core/djangoapps/django_comment_common``
* ``openedx/core/lib/xblock_builtin/xblock_discussion``

Ideally, what we want in the long term is for all of this extracted into a new repository that holds the code for both the inline discussion XBlock as well as all the Django apps.

That being said, it's not clear what the path forward for this app is. Forum functionality is something that has not been actively worked on for a while, and it's been suggested that we should remove this app altogether in favor of having better integration with other more established forum software. This decision is usually complicated by the desire to have tight integration with courseware and access to data for analytics.

Regardless, check with Product before undertaking any major refactoring work here.

Glossary
========

More Documentation
==================