direct: add FieldTriggers(); remove ClassifyChanges(), RecreateFields()#3595
Merged
direct: add FieldTriggers(); remove ClassifyChanges(), RecreateFields()#3595
Conversation
Collaborator
|
anton-107
approved these changes
Sep 11, 2025
shreyas-goenka
approved these changes
Sep 11, 2025
7556837 to
c4afdb7
Compare
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
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.
Changes
New method FieldTriggers(), which is a more powerful version of RecreateFields() that allows associate any action with a field.
Builds on top of #3585
Why
This covers existing classification use cases without custom code.
We might still need ClassifyChange function in the future, but exact types involved will likely change by that time (with regard to serialized plan work).
Tests
Existing tests.