edx-platform

Files

alangsto 9b204debf4 feat: check if profile name changes are valid for name affirmation. (#28697 )

MST-970. If name affirmation is enabled, a user should only be allowed to make limited edits to their profile name before they are required to go through IDV. Right now, the allowable edits are limited to:

* add/delete/replace one character (including one space on either side)

Edits that are not allowed, and therefore require IDV include:

* changing 2 or more characters
* changing their name 3 or more times

This behavior will not be enabled until name affirmation is fully rolled out, so there should be no noticeable difference in account settings behavior at the time this is merged.

2021-09-15 09:53:30 -04:00

accounts

feat: check if profile name changes are valid for name affirmation. (#28697 )

2021-09-15 09:53:30 -04:00

course_tag

refactor: Ran pyupgrade on openedx/core/djangoapps/user_api

2021-04-06 12:50:48 +05:00

management

build: Moved user and group management commands and unit tests to edx-django-utils

2021-08-30 12:03:37 +05:00

migrations

refactor: Ran pyupgrade on openedx/core/djangoapps/user_api

2021-04-01 19:34:01 +05:00

preferences

refactor: pyupgrade second iteration (#27460 )

2021-05-10 13:57:24 +05:00

templates/user_api/edx_ace/deletionnotificationmessage/email

Fix edx-ace templates

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

tests

chore: removed constraint on django-countries

2021-08-02 17:35:49 +05:00

verification_api

Refactor: Removed unused imports

2021-04-06 18:25:35 +05:00

__init__.py

Add base support for cohorted group configurations

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

admin.py

refactor: Ran pyupgrade on openedx/core/djangoapps/user_api

2021-04-01 19:34:01 +05:00

errors.py

refactor: Ran pyupgrade on openedx/core/djangoapps/user_api

2021-04-01 19:34:01 +05:00

helpers.py

refactor: Ran pyupgrade on openedx/core/djangoapps/user_api

2021-04-01 19:34:01 +05:00

legacy_urls.py

Refactor: Removed unused imports

2021-04-06 18:25:35 +05:00

message_types.py

refactor: Ran pyupgrade on openedx/core/djangoapps/user_api

2021-04-01 19:34:01 +05:00

middleware.py

Use full names for common.djangoapps imports; warn when using old style (#25477 )

2020-11-10 07:02:01 -05:00

models.py

Django3 has removed python_2_unicode_compatible.

2021-07-15 00:26:09 +05:00

partition_schemes.py

refactor: Ran pyupgrade on openedx/core/djangoapps/user_api

2021-04-01 19:34:01 +05:00

permissions.py

BOM-2329: Applied pylint-amnesty to system_wide_roles, theming, user_api, user_authn

2021-02-04 18:00:51 +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

Refactor: Removed unused imports

2021-04-06 18:25:35 +05:00

urls.py

feat: update account API to allow pending name changes

2021-09-01 11:26:43 -04:00

views.py

Refactor: Removed unused imports

2021-04-06 18:25:35 +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
==================