Closed nmrgt closed 6 months ago
The recent updates introduce significant enhancements to the carpool policy management system, focusing on integrating a new version of carpool data (v2). These changes include database migrations to add new columns and indices, updates to data seeding methods, and adjustments to data schemas and testing files to accommodate new identity and operator fields.
File Path | Change Summary |
---|---|
api/src/db/migrations/...update_policy_incentives.js |
Adds migration script for updating carpool policy incentives. |
api/src/db/migrations/policy/...migrate_to_carpool_v2.up.sql |
Alters policy.incentives table to add new columns and indices. |
api/src/pdc/providers/seed/Migrator.ts api/src/pdc/providers/seed/carpools.ts |
Updates to carpool data seeding methods and structure. |
api/src/pdc/services/policy/engine/helpers/limits.spec.ts |
Updates test references for passenger and driver identities, adds new operator fields. |
shared/acquisition/common/schemas/... shared/cee/common/ceeSchema.ts |
Modifies identity key validation in schemas to use a regular expression pattern. |
Objective | Addressed | Explanation |
---|---|---|
Support for carpool v2 in the policy service (#2475) | ✅ | |
Addition of "operator_journey_id" column (#2475) | ✅ | |
Utilization of carpool v2 data instead of policy.trip (#2475) | ✅ | |
Continued use of carpoolv1._id for backward compatibility (#2475) | ❓ | It's unclear if backward compatibility is maintained as the changes primarily focus on carpool v2. |
🐇 CodeRabbit's Ode to Carpool v2 🚗💨
In the land of code, where the bits align,
A new carpool version, v2, so fine!
With fields anew and schemas tight,
Our policies update through the night.
Here's to changes, big and small,
May our carpool data never stall!
api/src/pdc/services/cee/actions/ImportCeeIdentityAction.integration.spec.ts (1)
`44-44`: Ensure the `identity_key` is validated against the new regex pattern in the tests.Verification successful
--- The verification process has confirmed that the `identity_key` is indeed validated against the specified regex pattern in the `ImportCeeIdentityAction.integration.spec.ts` file. This aligns with the expectations set in the review comment, ensuring that the new field `identity_key` adheres to the necessary validation criteria within the test environment. **Conclusion:** - The `identity_key` validation against the regex pattern `[a-f0-9]{64}` is present in the test file as required.Scripts Executed
The following scripts were executed for the analysis: --- Script: ```shell #!/bin/bash # Description: Verify that the `identity_key` is validated against the regex pattern in the test file. # Test: Search for the regex pattern validation for `identity_key`. Expect: Matches. rg --files-with-matches --type typescript $'^[a-f0-9]{64}$' "api/src/pdc/services/cee/actions/ImportCeeIdentityAction.integration.spec.ts" ``` Length of output: 172 --- --- Script: ```shell #!/bin/bash # Description: Verify that the `identity_key` is validated against the regex pattern in the test file. # Test: Search for the regex pattern validation for `identity_key`. Expect: Matches. rg --files-with-matches 'identity_key.*[a-f0-9]{64}' "api/src/pdc/services/cee/actions/ImportCeeIdentityAction.integration.spec.ts" ``` Length of output: 208
fix #2475
Summary by CodeRabbit
New Features
Bug Fixes
Refactor
Documentation