edx-platform

Files

Régis Behmo 307457a255 Simplify hack to obtain waffle module names

Instead of going up the stacktrace to find the module names of waffle
flags and switches, we manually pass the module __name__ whenever the
flag is created. This is similar to `logging.getLogger(__name__)`
standard behaviour.

As the waffle classes are used outside of edx-platform, we make the new
module_name argument an optional keyword argument. This will change once
we pull waffle_utils outside of edx-platform.

Note that the module name is normally only required to view the list of
existing waffle flags and switches. The module name should not be
necessary to verify if a flag is enabled. Thus, maybe it would make
sense to create a `add` class methor similar to:

    class WaffleFlag:
        @classmethod
        def add(cls, namespace, flag, module):
            instance = cls(namespace, flag)
            cls._class_instances.add((instance, module))

2020-09-14 09:30:24 +02:00

accounts

Simplify hack to obtain waffle module names

2020-09-14 09:30:24 +02:00

config

BOM-1514 : Remove waffle switch PREVENT_AUTH_USER_WRITES (#23686 )

2020-04-10 18:21:12 +05:00

course_tag

Fix all E303 pep8 errors.

2019-12-30 12:25:38 -05:00

management

management command to retire a single user (#24188 )

2020-06-10 18:07:25 -04:00

migrations

Run 2to3 -f future . -w

2019-12-30 10:35:30 -05:00

preferences

~200k instances in last 7 days.

2020-03-12 14:22:52 +05:00

templates/user_api/edx_ace/deletionnotificationmessage/email

Fix edx-ace templates

2019-07-25 12:51:05 +05:00

tests

Merge pull request #22649 from edx/feanil/fix_pep8

2019-12-30 13:32:26 -05:00

verification_api

MST-348 Add the API to provide detailed ID Verification information (#24846 )

2020-08-26 17:23:04 -04:00

__init__.py

Add base support for cohorted group configurations

2014-12-05 09:52:26 -05:00

admin.py

Added more info to log in SSO request/response flow

2020-04-20 14:38:51 +05:00

errors.py

Implement client-side registration form validation.

2017-08-03 00:22:25 +05:00

helpers.py

Run 2to3 -f future . -w

2019-12-30 10:35:30 -05:00

legacy_urls.py

Fix all E303 pep8 errors.

2019-12-30 12:25:38 -05:00

message_types.py

Fix all E303 pep8 errors.

2019-12-30 12:25:38 -05:00

middleware.py

BOM-1121

2020-01-30 16:36:02 +05:00

models.py

~200k instances in last 7 days.

2020-03-12 14:22:52 +05:00

partition_schemes.py

Replace references to 'log.warn' with 'log.warning'

2020-06-18 12:08:15 -07:00

permissions.py

Run 2to3 -f future . -w

2019-12-30 10:35:30 -05:00

README.rst

update READMEs to clarify responsibilities

2019-12-16 13:51:43 -05:00

rules.py

Run 2to3 -f future . -w

2019-12-30 10:35:30 -05:00

serializers.py

MST-348 Add the API to provide detailed ID Verification information (#24846 )

2020-08-26 17:23:04 -04:00

urls.py

MST-348 Add the API to provide detailed ID Verification information (#24846 )

2020-08-26 17:23:04 -04:00

views.py

fixed deprecated django-filter features

2020-02-06 18:32:36 +05:00

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
==================