build: release v6.80.0

[wanlingt]

New

• feat: add index to myinfo child email response #6745
• build: merge v6.79.0 into develop #6765
• feat: add range validation to number field #6575
• fix: missing errors in error mapper #6764
• build: release v6.79.0 #6762

Dependencies

Dev-Dependencies

Tests

feat: add index to myinfo child email response #6745

@justynoh

Test for index - this can't be performed on Staging as the mockpass profiles only have 1 child, but can be tested locally

• On a MyInfo form, add 2 child fields. Enable multiple children for the first child field
• Open the form
• For the first child field, add another child
• Fill in the form (there should be 3 children entries in total) and submit it
• The child fields in the email response should be numbered according to the child's index, e.g. [MyInfo] Child 1 Name

Regression test

• Add all MyInfo fields to a form
• Fill in the form and submit it
• There should be no change in the format of the MyInfo field names, other than the child field. The child field (assuming there's just 1) should be named in this format [MyInfo] Child e.g. [MyInfo] Child 1 Name

feat: add range validation to number field #6575

@wanlingt
Manual tests for range validation:

• E2E: Range validation works as expected.
  • Select Range of values allowed under Field restriction.
    • Submit the form without entering a minimum or maximum value. This should display an error.
    • Submit the form with input 0 for minimum or maximum value. This should display an error.
    • Submit the form with an invalid range where minimum >= maximum value. This should display an error.
    • Submit the form with only one of minimum and maximum value specified. This should work and create a number field as expected.
    • Submit the form with a valid range where minimum < maximum. This should work and create a number field as expected.

Regression tests (for EditNumber.tsx)

• E2E: Try to create a number field with no selected validation. This should work and create a number field as expected.
• E2E: Existing number validation still works as expected.
  • Select Number of characters allowed under Field restriction.
    • Submit the form without choosing length validation. This should display an error.
  • Select Min/Max/Exact for length validation.
    • Submit the form without an input for Number of characters. This should display an error.
    • Submit the form with 0 as the input. This should display an error.
    • Submit the form with a number > 0 as the input. This should work and create a number field as expected.

Deploy notes

New scripts:

• migrate-number-field-schema.js: This script migrates ValidationOptions to ValidationOptions.LengthValidationOptions for all existing number form fields.

fix: missing errors in error mapper #6764

@wanlingt

• Go to a storage mode form with at least 1 attachment field.
• Open the network panel.
• Make a submission with at least 1 attachment.
• Copy the cURL request of the above submission.
• In a terminal, paste this request and remove the file extensions in both the answer and the file field at the end. This is to simulate an invalid file extension (since there will be no file extensions).
• Add the -I flag to the cURL request.
• Enter the request. The status code should be 400 and the message should be "There is something wrong with your form submission. Please check your responses and try again. If the problem persists, please refresh the page."

[LinHuiqing]

thanks @justynoh and @wanlingt for testing!