It is now possible to refer to the input node of a LOOP macro using LOOP.inputNode expression, removing the need to use a VAR macro. The index of the LOOP can also be accessed under the same namespace, using LOOP.index , replacing the previous user defined context variable.
It is now possible to switch off the scrolling synchronization of the editors in the Diff dialog using the dedicated button.
The MPS model viewer is enabled for the merge commits in git log. The viewer shows three panels - the center panel for the merged model and left and right panels for the models of two merged branches.
The root annotation and root/node history algorithm was based on the iteration over the ordered list of file revisions. The changes for the root were calculated between two adjacent revisions. It could happen that these revisions were from two different branches. In this case the obtained changes make no sense. Merge revisions were not handled correctly as well. The changes from the older revisions could be erroneously displayed as changes from the newer merge revision. Therefore, the revisions graph should be considered for calculating the correct history of the changes rather than a simple list.
The lang.text language has been enhanced with several new capabilities, which directly enhances the single and multi-line comments in BaseLanguage.
The method signature refactoring dialog now includes a way to specify default values for new arguments or arguments whose type has changed. When a parameter is removed but is still used in the method, a new local variable is introduced so the reference is not lost. In addition, vararg typed parameters are now handled.
When the call of a method does not match its signature, an intention allows to change the method signature according to the call. This intention has been improved to map the existing parameters in a smart way, so a maximum amount of existing parameters are reused and their references kept.
model.nodesIncludingImported() now support #expression to specify concepts, much like
model.nodes() did for quite a while. https://youtrack.jetbrains.com/issue/MPS-32743
For Generators, there's an option to check whether nodes template produce fit into proper role of a parent node. The option if available in Generator Preferences in IDE as well as through build project settings. Generator may issue a warning, which usually indicates there's some inconsistency in templates, e.g. improperly placed
Template Fragment or
COPY-SRC annotation. Compiled templates, however, didn't perform the check, rendering the option useless. With 2021.1, compiled templated go an extra mile to check proper child placement into a parent if the option is active.
SNode.setReference(SReferenceLink, SNodeReference) to avoid going through
SReference.create() factory method
Now, when MPS creates a new project, we write indicator of actual version into project descriptor so that Migration Assistant doesn't try to apply older project migration than the one indicated with baseline. Project Migration implementation indicate which minimum baseline version they need to run.
No longer JUnit3 and its
junit.framework.TestCase superclass limitation.