model contexts with two variable expressions

If you have selected something at the first step, the variable or expression will be displayed in the Expression field. Select Evaluate Expression from the context menu.Ĭhoose Run | Debugging Actions | Evaluate Expression from the main menu.Ĭlick on the toolbar of the Debug window. Open the Evaluate dialog in one of the following ways: If you want to start with some expression or a variable, select it in the editor or in any view in the Debug window. In other words, if JetBrains Rider stops at a breakpoint within a method called from the Expression Evaluation, you cannot use the Expression Evaluation feature again. While evaluating expressions, mind the followingĪ method can be invoked in the Evaluate dialog only if the debugger has stopped at a breakpoint, but has not been paused.Įxpression evaluation can only be 'single-level'. The Evaluate dialog is non-modal, so you can switch the focus back to the editor to copy other variables and expressions, and you can also open multiple Evaluate dialogs if necessary.Įvaluation of arbitrary expressions and much more is also available in the Immediate Window. The Evaluate dialog lets you play with variables and expressions in the current context - you can perform various operations and call methods on them, and then analyze results that you get with their current valuesįor example, if there is a String myString variable in the current context, you can enter the following expression to check whether the current value of the variable contains a substring: myString.Contains('text') You can also invoke the value tooltip on a variable, expression, or selection with the Quick Evaluate Expression command ( Control+Alt+F8 or Run | Quick Evaluate Expression or Alt-click ).Įvaluate arbitrary expressions in the dedicated dialog You can extend or shrink the selection with Control+W / Control+Shift+W thus changing the evaluated expression: When Show value tooltip on code selection is enabled on the Build, Execution, Deployment | Debugger | Data Views page of the IDE settings Control+Alt+S JetBrains Rider shows the evaluation result for the selected expression. If the debugged code contains properties with computationally expensive calls in their getters, or when property getters may change the program state or have other side effects, you may want to disable automatic property evaluation by clearing the Allow property evaluations and other implicit function calls checkbox on the Build, Execution, Deployment | Debugger page of the IDE settings Control+Alt+S. When Show value tooltip is enabled on the Build, Execution, Deployment | Debugger | Data Views page of the IDE settings Control+Alt+S, you can hover over variables and expressions to see the evaluated results:

If the value of a variable or an expression contains child elements, clicking expands the node and displays all children. The easiest way to evaluate expressions is to use editor tooltips.

If we still need to use the firstArticle variable inside the secondDiv, we would need to define it again in secondDiv or wrap these two div tags in a common element and define the firstArticle in it.With JetBrains Rider, you can not only view values of separate variables, but also evaluate more complex expressions, such as method calls, operator expressions, lambda expressions, and anonymous classes.Įxpressions are evaluated in the context of a stack frame currently selected in the Debug window. This is because the element is trying to use a variable defined in the firstDiv, which is out of scope. We’ll get an exception during compile-time saying that the firstArticle is null: .SpelEvaluationException: EL1007E: Property or field 'name' cannot be found on null On the other hand, when we try to use the firstArticle in another div: They can be used only within the range of the element that they were defined in.įor example, the below code is correct as the element is within the firstDiv: On the other hand, variables defined in the HTML template have a local scope. This means they can be used in every place of our HTML templates. Variables passed to the Model in a controller have a global scope.

Model contexts with two variable expressions