@ministryofjustice/hmpps-prison-permissions-lib 2.3.0 → 2.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +16 -0
- package/dist/index.cjs +942 -858
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.ts +5 -1
- package/dist/index.esm.js +942 -858
- package/dist/index.esm.js.map +1 -1
- package/dist/services/permissions/PermissionsLogger.d.ts +1 -0
- package/dist/services/permissions/PermissionsService.d.ts +4 -1
- package/dist/services/permissions/utils/PermissionUtils.d.ts +3 -1
- package/dist/testUtils/PrisonerPermissionsMock.d.ts +1 -5
- package/package.json +6 -6
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,22 @@
|
|
|
2
2
|
|
|
3
3
|
Please use this to capture reasoning behind changes:
|
|
4
4
|
|
|
5
|
+
## 2.4.0
|
|
6
|
+
|
|
7
|
+
The Connect DPS team have been supporting a request to make duplicate prisoner records more visible to users.
|
|
8
|
+
The policy is that if a prisoner record is a duplicate of a record that a user has access to, then the user should
|
|
9
|
+
have read-only access to the duplicate record if they wouldn't otherwise have had access. This allows users to see if
|
|
10
|
+
there is any relevant information in the duplicate record that they may need to be aware of when working with the
|
|
11
|
+
prisoner.
|
|
12
|
+
|
|
13
|
+
This release introduces support for this policy in the permissions library. The client currently needs to supply
|
|
14
|
+
a list of prisoner search results for the duplicate prisoner records by placing them in
|
|
15
|
+
`req.middleware.duplicatePrisonerData`. Duplicate prison numbers are found by making a request to the
|
|
16
|
+
`hmpps-person-record` API. This is optional, if the client does not provide this data then the
|
|
17
|
+
library will continue to function as before but without any additional access to duplicate records.
|
|
18
|
+
|
|
19
|
+
When a required permission is upgraded by a duplicate record, this is logged for audit purposes.
|
|
20
|
+
|
|
5
21
|
## 2.3.0
|
|
6
22
|
|
|
7
23
|
Adding an extra option `readOnly` to the `PermissionsService` which defaults to `false`. When set to `true`, this
|