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

Refactor handleRollups because merging could fail #1518

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

aheber
Copy link
Contributor

@aheber aheber commented Feb 4, 2025

Changes

  • bugfix: refactor merging to better support case merge and keep scenario

Issues Closed

Cases allow to merge without delete. Merge handling logic was never refactored to allow for this.
@aheber aheber requested a review from octatau February 4, 2025 03:10
@aheber
Copy link
Contributor Author

aheber commented Feb 4, 2025

@octatau if you have some time to review this one.

There is a lot of code moved so the diff is a bit tricky to work through. Mostly I changed where the handling for created/deleted trigger (either new or old is empty) and I unwrapped the per-record checks from an if statement.

I added a bunch of new tests around merging that seem to cover all the scenarios I could think of.

@aheber aheber merged commit ab605ec into main Feb 10, 2025
3 checks passed
@aheber aheber deleted the feature/1038-case-merge-error-when-parent-object branch February 10, 2025 14:52
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.

2 participants