Fix validations not actually running against changes - #4574
Merged
Conversation
We were avoiding committing a session when validating new objects, but this also meant we weren't actually applying changes to them. This was only affecting a few instances in production, but would have affected a lot more due to the changes in #4573 (which was never deployed). We now apply changes to an object regardless of whether we can use begin_nested().
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We were avoiding committing a session when validating new objects, but this also meant we weren't actually applying changes to them. This was only affecting a few instances in production, but would have affected a lot more due to the changes in #4573 (which was never deployed). We now apply changes to an object regardless of whether we can use begin_nested().
Also adds an alert to the showcase application page if you already have a studio registered, which is how we found this issue.