Repeat multi field nl8 form change - #1417
Open
micolgiannelli2 wants to merge 935 commits into
Open
Conversation
…-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
…defect included full stops
Accessibility issues with links
…act_message patch: Add kls contact email on 500 page
…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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This template is designed to help both contributors and maintainers. It is a checklist to ensure all necessary
information is provided, and prompts contributors on any contribution guidelines they have missed.
Do not remove sections.
They are important for the review process and help maintainers ensure quality and good documentation across the
project.
Some checkboxes will not apply to every change, so feel free to leave them unchecked if they are not relevant.
Description
Context
TODO..
Changes
Type of change
What is the type of change you are making?
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?
Testing
Automated tests
Have you added automated tests?
Manual tests
Have you manually tested your changes?
Have you attached an example form JSON or snippet for the reviewer in this PR?
Steps to test
Documentation
Have you updated the documentation?
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?