Skip to content

Commit a3fa482

Browse files
author
John Bramley
authored
remove user model va_profile (department-of-veterans-affairs#24204)
* remove user model va_profile * removes extra ADR file
1 parent db83a74 commit a3fa482

File tree

2 files changed

+24
-0
lines changed

2 files changed

+24
-0
lines changed

.adr-dir

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
docs/adr
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# 7. remove user model va_profile
2+
3+
Date: 2021-05-04
4+
5+
Whom:
6+
- John Bramley
7+
- Trevor Bosaw
8+
9+
## Status
10+
11+
Pending
12+
13+
## Context
14+
15+
As part of the larger effort to [refactor the User & Identity on vets-api](https://app.zenhub.com/workspaces/vsp-identity-5f5bab705a94c9001ba33734/issues/department-of-veterans-affairs/va.gov-team/21012), we have decided to more tightly control access to user attributes through specific & improved getter methods. The `va_profile` methods on the User class revealed too much information about a user's MPI profile and has been rendered uneccessary by the updated getter methods.
16+
17+
## Decision
18+
19+
The decision made is to transfer the User's `va_profile_status` and `va_profile_error` methods to `mpi_status` and `mpi_error` since that is what they are abstractions of, and to remove the `va_profile` method entirely in favor of relying on getter methods for specific attributes.
20+
21+
## Consequences
22+
23+
We expect this to streamline and simplify interaction with a user's attributes; the rest of vets-api will increasingly be able to invoke the getter method for a specific attribute and be confident that the value returned is the one it wants instead of having to directly involve itself in where and how that attribute value was obtained.

0 commit comments

Comments
 (0)