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
When the user renames any "NamedElement" like, for instance, a DataType, an entry in a Context Expression, or a Decision Node, all places where referencing that element should be updated to the new name.
"All places" mean "all FEEL expressions".
Confirmation Dialog
As discussed in the private chat, the rename could result in a refactoring or not, because it is not always that user may want to perform a refactor.
The user may not want to perform a refactor; they can just rename the named object to something else and create a new object with the older name to replace it.
So, for this scenario, we should ask for confirmation from the user, with the following dialog:
The confirmation dialog should behave as the following:
When renaming some node, it shows the dialog if the node is being referenced in an expression
When renaming some data type, it shows the dialog if the data type is being referenced in an expression
When renaming an included model (in the Included Models tab), it does not show the dialog, because doesn't make any sense in my opinion to not update the references in this case, since this already was the default behavior before this PR (when we renamed a included model, we already updated all the references except the expressions, now we update the expressions).
Acceptance criteria:
All the following renames should also perform a refactor if the user wants to by confirming in the confirmation dialog:
In DMN editor:
Rename the input nodes
Rename the nodes by the properties panel
Rename business knowledge nodes
Rename business knowledge nodes by properties panel
Rename decision nodes
Rename decision by properties panel
Rename data types
In Boxed Expression Editor
Rename context
Rename the "some" variable in the "Some" expression
Rename the "every" variable in the "Every" expression
Rename the header of expressions
Rename the header of expressions by properties panel
The following refactor should be performed without asking confirmation:
Rename an included model
The text was updated successfully, but these errors were encountered:
When the user renames any "NamedElement" like, for instance, a DataType, an entry in a Context Expression, or a Decision Node, all places where referencing that element should be updated to the new name.
"All places" mean "all FEEL expressions".
Confirmation Dialog
As discussed in the private chat, the rename could result in a refactoring or not, because it is not always that user may want to perform a refactor.
The user may not want to perform a refactor; they can just rename the named object to something else and create a new object with the older name to replace it.
So, for this scenario, we should ask for confirmation from the user, with the following dialog:
The confirmation dialog should behave as the following:
Acceptance criteria:
All the following renames should also perform a refactor if the user wants to by confirming in the confirmation dialog:
In DMN editor:
In Boxed Expression Editor
The following refactor should be performed without asking confirmation:
The text was updated successfully, but these errors were encountered: