APS-1314 - Return User's CRU Management Area details in the API #2315
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davidatkinsuk
force-pushed
the
feature/aps-1314-update-api-to-return-user-area-details
branch
3 times, most recently
from
ed52bfb to
a93b17c
Compare
davidatkinsuk
changed the title
davidatkinsuk
force-pushed
the
feature/aps-1314-update-api-to-return-user-area-details
branch
from
a93b17c to
9b98e4b
Compare
davidatkinsuk
force-pushed
the
feature/aps-1314-update-api-to-return-user-area-details
branch
from
9b98e4b to
c48f74a
Compare
davidatkinsuk
changed the title
davidatkinsuk
force-pushed
the
feature/aps-1314-update-api-to-return-user-area-details
branch
4 times, most recently
from
17573b5 to
4dcc1a1
Compare
davidatkinsuk
force-pushed
the
feature/aps-1314-update-api-to-return-user-area-details
branch
4 times, most recently
from
24f74d2 to
ca8a6f8
Compare
This commit adds CRU Management Area fields to the ApprovedPremisesUser API Model to support: * Determining which CRU Management Area the user is in (when retrieved via /profile/v2) * Logic to determine/set/get override configuration for the user management page This commit is quite large because i had fix existing test data where entries in the users table were created for CAS1 testing and the CRU Management Area was not set, something which wouldn’t be the case in production (it’s logically mandatory for CAS1 users).
davidatkinsuk
force-pushed
the
feature/aps-1314-update-api-to-return-user-area-details
branch
from
ca8a6f8 to
8a33399
Compare
davidatkinsuk
deleted the
feature/aps-1314-update-api-to-return-user-area-details
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds CRU Management Area fields to the ApprovedPremisesUser API Model to support:
This commit is quite large because i had fix existing test data where entries in the users table were created for CAS1 testing and the CRU Management Area was not set, something which wouldn’t be the case in production (it’s logically mandatory for CAS1 users)