Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CAS1 endpoints for departure, move on and non arrival reasons #2822

Merged
merged 3 commits into from
Jan 17, 2025

Conversation

davidatkinsuk
Copy link
Contributor

@davidatkinsuk davidatkinsuk commented Jan 17, 2025

This PR also converts some wild-carded reasons into CAS-specific reasons, allowing us to disable them for CAS1 without affecting CAS3.

@davidatkinsuk davidatkinsuk force-pushed the feature/aps-1756-add-cas1-ref-data-endpoints branch from 7edc475 to ba75224 Compare January 17, 2025 10:02
@davidatkinsuk davidatkinsuk changed the title Add /cas1/reference-data/departure-reasons Add CAS1 endpoints for departure, move on and non arrival reasons Jan 17, 2025
@davidatkinsuk davidatkinsuk force-pushed the feature/aps-1756-add-cas1-ref-data-endpoints branch 2 times, most recently from 6af7b22 to 5b3fd1c Compare January 17, 2025 11:01
@davidatkinsuk davidatkinsuk marked this pull request as ready for review January 17, 2025 11:01
@davidatkinsuk davidatkinsuk force-pushed the feature/aps-1756-add-cas1-ref-data-endpoints branch from 5b3fd1c to c02e91f Compare January 17, 2025 11:38
This should be used instead of the service-agnostic endpoint, which can return unexpected results due to the amiguous SQL being used (this is documented in this commit).

Instead of ‘fixing’ the amiguous SQL and potentially disrupting CAS3, we’ve instead introduced a CAS1 specific version of the SQL/endpoint

This commit also ‘splits’ a wildcarded departure reason to instead have CAS1 and CAS3 specific reasons. The existing reason was change to belong to CAS3 to avoid disrupting CAS3. This allows us to disable the reason for CAS1 without affecting CAS3
We also deprecate the ‘shared’ version of the endpoint, which is only used by CAS1 currently anyway
This should be used instead of the service-agnostic endpoint, which can return unexpected results due to the SQL being used. Instead of ‘fixing’ the SQL and potentially disrupting CAS3, we’ve instead introduced a CAS1 specific version.
@davidatkinsuk davidatkinsuk force-pushed the feature/aps-1756-add-cas1-ref-data-endpoints branch from c02e91f to 6bfddc2 Compare January 17, 2025 11:41
@davidatkinsuk davidatkinsuk merged commit 69975b4 into main Jan 17, 2025
8 checks passed
@davidatkinsuk davidatkinsuk deleted the feature/aps-1756-add-cas1-ref-data-endpoints branch January 17, 2025 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants