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

Lookup the right field in FieldsWillMerge #5268

Merged
merged 1 commit into from
Mar 8, 2025

Conversation

rmosolgo
Copy link
Owner

@rmosolgo rmosolgo commented Mar 8, 2025

Fixes #5264

@rmosolgo rmosolgo added this to the 2.4.12 milestone Mar 8, 2025
@rmosolgo rmosolgo merged commit 94440dc into master Mar 8, 2025
14 checks passed
@AlenaSviridenko
Copy link

@rmosolgo I was wondering how much of the work would it be to backport this to the next patch version of 2.3?
We are looking into upgrading gem to 2.3.21, but it contains this bug, which effect is hard to predict.
Thank you!

@rmosolgo
Copy link
Owner Author

It looks like it cherry-picks cleanly: #5275

@rmosolgo rmosolgo deleted the fix-fields-will-merge-alias-on-fragment branch March 13, 2025 13:30
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.

No validation error anymore on conflicting aliases?
2 participants