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

Don't insert updated replacement result #2089

Merged
merged 8 commits into from
Nov 13, 2023
Merged

Don't insert updated replacement result #2089

merged 8 commits into from
Nov 13, 2023

Conversation

hannobraun
Copy link
Owner

From a commit message:

This makes replace operations more flexible, as it gives control over insertion to the caller. This is especially relevant, if the replacement produces an invalid intermediate step. Currently, everything that is inserted is validated, and validation provides no good mechanism to deal with invalid intermediate objects, even if the final object ends up being valid.

This is required for making the next steps on #2023.

Those will be used to adjust the return type, making the replace traits
more flexible.
This makes replace operations more flexible, as it gives control over
insertion to the caller. This is especially relevant, if the replacement
produces an invalid intermediate step. Currently, everything that is
inserted is validated, and validation provides no good mechanism to deal
with invalid intermediate objects, even if the final object ends up
being valid.
@hannobraun hannobraun enabled auto-merge November 13, 2023 12:46
@hannobraun hannobraun merged commit c91347f into main Nov 13, 2023
4 checks passed
@hannobraun hannobraun deleted the replace branch November 13, 2023 12:54
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.

1 participant