You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a ChangeProcessor has to return Commands that can be executed afterwards.
It makes no sense that the transformation developer (the one who defines ChangeProcessors) has to think about creating commands, but just wants to define change propagating routines that are executed correctly.
We have to move the logic for creating commands to the Change2CommandTransforming and let the ChangeProcessor simply define a method that executes a change propagation.
The text was updated successfully, but these errors were encountered:
Currently, a ChangeProcessor has to return Commands that can be executed afterwards.
It makes no sense that the transformation developer (the one who defines ChangeProcessors) has to think about creating commands, but just wants to define change propagating routines that are executed correctly.
We have to move the logic for creating commands to the Change2CommandTransforming and let the ChangeProcessor simply define a method that executes a change propagation.
The text was updated successfully, but these errors were encountered: