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

regression: Do not throw an error when a required custom field is missing on visitor to contact migration #34071

Merged
merged 1 commit into from
Nov 28, 2024

Conversation

matheusbsilva137
Copy link
Member

@matheusbsilva137 matheusbsilva137 commented Nov 27, 2024

Proposed changes (including videos or screenshots)

Introduced here: #32727

  • Skip custom fields validation on contact migration (since it has already been applied when mapping a visitor to a contact). Keeping this validation causes RC to throw an error in case the legacy visitor doesn't contain a field that is now required (which is unintended for this specific flow).

Issue(s)

Steps to test or reproduce

Further comments

On visitor to contact migration, we shouldn't throw errors in any of these cases:

  • A custom field has been made required after updating to 7.1;
  • A custom field has been removed after updating to 7.1;

#34030 has only partially fixed this issue (the second item has been addressed, but not the first one). In order to not throw errors on visitor to contact migration, we should skip the whole repeated validation process so that missing required fields do not generate an error.

SCI-179

@matheusbsilva137 matheusbsilva137 added this to the 7.1.0 milestone Nov 27, 2024
Copy link
Contributor

dionisio-bot bot commented Nov 27, 2024

Looks like this PR is ready to merge! 🎉
If you have any trouble, please check the PR guidelines

Copy link

changeset-bot bot commented Nov 27, 2024

⚠️ No Changeset found

Latest commit: cf14131

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

PR Preview Action v1.4.8
🚀 Deployed preview to https://RocketChat.github.io/Rocket.Chat/pr-preview/pr-34071/
on branch gh-pages at 2024-11-27 22:59 UTC

Copy link

codecov bot commented Nov 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.75%. Comparing base (fad7de4) to head (cf14131).
Report is 1 commits behind head on release-7.1.0.

Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff               @@
##           release-7.1.0   #34071   +/-   ##
==============================================
  Coverage          75.75%   75.75%           
==============================================
  Files                510      510           
  Lines              22078    22078           
  Branches            5387     5387           
==============================================
  Hits               16726    16726           
  Misses              4706     4706           
  Partials             646      646           
Flag Coverage Δ
unit 75.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@matheusbsilva137 matheusbsilva137 marked this pull request as ready for review November 27, 2024 23:42
@matheusbsilva137 matheusbsilva137 requested a review from a team as a code owner November 27, 2024 23:42
@matheusbsilva137 matheusbsilva137 added the stat: QA assured Means it has been tested and approved by a company insider label Nov 28, 2024
@dionisio-bot dionisio-bot bot added the stat: ready to merge PR tested and approved waiting for merge label Nov 28, 2024
@kodiakhq kodiakhq bot merged commit 2b05900 into release-7.1.0 Nov 28, 2024
56 checks passed
@kodiakhq kodiakhq bot deleted the regression/custom-fields-required-error branch November 28, 2024 01:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stat: QA assured Means it has been tested and approved by a company insider stat: ready to merge PR tested and approved waiting for merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants