edx-platform

Files

Troy Sankey 212d17bbf3 email opt-in mgmt command: Disable the course lookup if a list is provided

This is cherry-picked verbatim from
zafft/analytics-exporter-settings-hotfix (#18530).  I'm fear that
without merging these changes upstream, a larger set of courses will be
consdiered for processing, and that would alter the behavior of the
analytics-email-optin-* jobs.

2020-09-17 17:34:24 -04:00

accounts

…

config

…

course_tag

…

management

email opt-in mgmt command: Disable the course lookup if a list is provided

2020-09-17 17:34:24 -04:00

migrations

…

preferences

…

templates/user_api/edx_ace/deletionnotificationmessage/email

…

tests

…

verification_api

…

__init__.py

…

admin.py

…

errors.py

…

helpers.py

…

legacy_urls.py

…

message_types.py

…

middleware.py

…

models.py

…

partition_schemes.py

…

permissions.py

…

README.rst

…

rules.py

…

serializers.py

…

urls.py

…

views.py

…

README.rst

Status: Active

Responsibilities
================
The user_api app is currently a catch all that is used to provide various apis that are related to the user and also to features within the platform.

Intended responsibility: To manage user profile and general account information and to provide APIs to do so easily. This includes the following features: user preference, user profile, user retirement, and account activation/deactivation.

Direction: Decompose
===============
Currently this app is a catch all for many user related information even when that information should really belong in a different app.  If you are building a feature and need to provide information about a user within the context of your feature, you should localize that API to your feature and make your assumptions about what user information you need clear.

For example authentication related APIs have already been moved to the user_authn django app.

Glossary
========

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