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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: data migration for styling fixes #2640

Merged
merged 5 commits into from
May 16, 2024
Merged

fix: data migration for styling fixes #2640

merged 5 commits into from
May 16, 2024

Conversation

pandeymangg
Copy link
Contributor

What does this PR do?

Fixes a bug in the data migration script which leads to ignoring the product overwrites for the products that have default styling

Fixes #2625 (issue)

How should this be tested?

  • Test A
  • Test B

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read How we Code at Formbricks
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand bits
  • Ran pnpm build
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues
  • First PR at Formbricks? Please sign the CLA! Without it we wont be able to merge it 馃檹

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the Formbricks Docs if changes were necessary

Copy link

vercel bot commented May 16, 2024

The latest updates on your projects. Learn more about Vercel for Git 鈫楋笌

2 Ignored Deployments
Name Status Preview Comments Updated (UTC)
formbricks-cloud 猬滐笍 Ignored (Inspect) Visit Preview May 16, 2024 4:04pm
formbricks-docs 猬滐笍 Ignored (Inspect) Visit Preview May 16, 2024 4:04pm

@github-actions github-actions bot added the bug Something isn't working label May 16, 2024
Copy link
Contributor

github-actions bot commented May 16, 2024

Thank you for following the naming conventions for pull request titles! 馃檹

Copy link
Member

@mattinannt mattinannt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pandeymangg thanks for the PR :-) Looks good in general; I only have small suggestions for improvements :-)


for (const survey of surveysWithProductOverwrites) {
if (survey.productOverwrites) {
const { brandColor, highlightBorderColor, ...rest } = survey.productOverwrites;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would it make sense to add a check here if brandColor & highlightColor is defined and only then update the survey. Because otherwise if the data-migration runs multiple times the surveys will be updated again.

Copy link
Member

@mattinannt mattinannt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pandeymangg thanks for making the changes; looks great!! 馃槉馃挭

@mattinannt mattinannt added this pull request to the merge queue May 16, 2024
Merged via the queue into main with commit 0b87d35 May 16, 2024
12 checks passed
@mattinannt mattinannt deleted the fix/styling-fixes branch May 16, 2024 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] color change after upgrade
2 participants