Skip to content

[NL8 only non prod] Core Aipm Form change - #1415

Open
micolgiannelli2 wants to merge 945 commits into
XGovFormBuilder:mainfrom
ukhsa-collaboration:micol/core-aipm-form-integration-srs
Open

[NL8 only non prod] Core Aipm Form change#1415
micolgiannelli2 wants to merge 945 commits into
XGovFormBuilder:mainfrom
ukhsa-collaboration:micol/core-aipm-form-integration-srs

Conversation

@micolgiannelli2

Copy link
Copy Markdown

Description

Introducing new core aipm functionality to nl8 form (SRS dev environment)

Context

TODO..

Changes

  • Change A
  • Change B

Type of change

What is the type of change you are making?

  • Chore or documentation (non-breaking change that does not add functionality)
  • ADR (Architectural Decision Record, non-breaking change that documents or proposes a decision)
  • Refactor (non-breaking change that improves code quality)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

PR title

PR titles should be prefixed with the type of change you are making, based on the README.md#versioning.
This is so that when performing a squash merge, the PR title is automatically used as the commit message.

Have you updated the PR title to match the type of change you are making?

  • Yes
  • No, I need help or guidance

Testing

Automated tests

Have you added automated tests?

  • Yes, unit or integration tests
  • Yes, end-to-end (cypress) tests
  • No, tests are not required for this change
  • No, I need help or guidance
  • No (explain why tests are not required or can't be added at this time)

Manual tests

Have you manually tested your changes?

  • Yes
  • No, manual tests are not required or sufficiently covered by automated tests

Have you attached an example form JSON or snippet for the reviewer in this PR?

  • Yes
  • No, any existing form can be used
  • No, it is not required or not applicable

Steps to test

  1. Step 1
  2. Step 2

Documentation

Have you updated the documentation?

  • Yes, I have updated ./docs for this change since additional explanation or steps to use/configure the feature is required
  • Yes, I have added or updated an ADR for this change since it is large, complex, or has significant architectural implications
  • Yes, I have added inline comments for hard-to-understand areas
  • No, I am not sure if documentation is required
  • No, documentation is not required for this change

Discussion

Warning

Large or complex changes may require discussion with the maintainers before they can be merged. If it has not yet been discussed, it may delay the review process

Have you discussed this change with the maintainers?

  • Yes, I have discussed this change with the maintainers on slack, email or via GitHub issues
  • Yes, this change is an ADR to help kick-off discussion
  • No, this change is small and does not require discussion
  • No, I am not sure if one is required

ebadian and others added 30 commits December 19, 2025 09:22
…-break-page

Reordering list and adding details with style
…dd-east-midlands

RITM0197916 Enable East Midlands in RaO Frontend
…dd-east-midlands

Update value to include HPT
…dition

New Feture - form update - Micol KLS front pages forms
…ndment

defect fix (text only non functional) - start page amendment
…artbeat (#541)

There was a mismatch between frontend inactivity tracking and the server-side session stored in Redis. While the frontend treated user interaction (mouse movement, typing, scrolling) as activity, the Redis session TTL was only refreshed on page navigation or submission.

This change introduces a lightweight client-side session heartbeat that runs on every form page. The heartbeat listens for user interaction and periodically calls a /session/keep-alive endpoint, which refreshes the Redis session TTL without modifying session state.

This keeps Redis session expiry aligned with real user activity and prevents active users from being logged out or losing progress.
…defect

Defects in new training form start page
micolgiannelli2 and others added 30 commits July 8, 2026 11:56
…urls

Dynamic Disease name form changes + Template render in summary and detail components
…Evaluation

AI evaluation completed and repo is Ai safe and ready
…per-project

feature: added project specific error page resolution
…ls-delete-clean

FORM ONLY CHANGE NL8 NL5 NON PROD - QUERY PARAMS ENV UPGRADE
…rade-nl5

[NL5 form only chanage] - upgrade nl5 to remove personal details
…a53d357a6f5296ee9d689

[Snyk] Security upgrade tmp from 0.2.1 to 0.2.3
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.