{"id":331552,"date":"2023-03-10T15:45:24","date_gmt":"2023-03-10T14:45:24","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=dotnet&p=331552"},"modified":"2023-03-10T16:42:52","modified_gmt":"2023-03-10T15:42:52","slug":"rider-2023-1-eap-8","status":"publish","type":"dotnet","link":"https:\/\/blog.jetbrains.com\/dotnet\/2023\/03\/10\/rider-2023-1-eap-8\/","title":{"rendered":"Rider 2023.1 EAP 8 Is Here With Improved C# and F# Support, New Editor Features and Fixes for Unity"},"content":{"rendered":"\n

The Early Access Program for Rider 2023.1 has brought many exciting updates to your favorite .NET IDE, and the EAP 8 build that\u2019s just been released is yet another step on our path toward the next stable release.<\/p>\n\n\n\n

Before you download<\/a> it, let\u2019s take a look at the updates in this build.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

C# support<\/h2>\n\n\n\n

Insert a return type specification for lambdas<\/h3>\n\n\n\n

Lambda expressions in C# usually have implicitly-typed parameters and an inferred return type. Sometimes, it can be useful to add explicit types in a signature of a lambda expression to make code clearer or to help C# type inference in some complex scenarios involving overload resolution. A context action to insert parameter types, Insert parameter signature<\/em>, has been around <\/em>for a while.<\/p>\n\n\n\n

Starting from C# 11, adding a return type specification for lambda expressions is also possible. To accomplish this, we introduced a new context action, Insert return type specification,<\/em> in version 2023.1. You can apply it to all lambda expressions in scopes like method, class, file, project, or an entire solution.<\/p>\n\n\n\n\n\n\n\n

Syntax style for null checking patterns<\/h3>\n\n\n\n

We provided the new “Syntax style” setting to help you enforce one consistent style of not null<\/em> checks inside patterns. It consists of 2 options: empty recursive pattern syntax { } and negated pattern not null, where the latter is set by default. You can adjust this behavior by going to Settings\/Preferences | Editor | Code Style | C# | Syntax Style <\/em>tab. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n\n\n\n\n

There is a disadvantage to using the not null <\/code>pattern \u2013 you cannot introduce variable names for the checked value as you can with the recursive pattern { LastName: { } lastName }<\/code>. Workarounds like { LastName: not null and var lastName }<\/code> are not as concise as a recursive pattern. <\/p>\n\n\n\n

To help resolve this, we’ve added the Add pattern variable<\/em> context action over the not null pattern. This Add pattern variable<\/em> context action now looks for expressions accessing the same value (since we are introducing a variable name) and replacing all of them with the newly introduced name to consolidate all accesses to the same value.<\/p>\n\n\n\n\n\n\n\n

ArgumentNullException.ThrowIfNull style of null checks<\/h3>\n\n\n\n

.NET 6.0 SDK introduced a new API for null checking \u2013 ArgumentNullException.ThrowIfNull<\/code>. Our code analysis engine has recognized this checking approach since then, but there was no option to use this API as a default style of null<\/code> checks produced in Rider. In the 2023.1 release, we added an ArgumentNullException.ThrowIfNull<\/code> pattern to Settings\/Preferences | Editor | Code Style | C# | Null checking<\/em> for Rider.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Pattern is redundant<\/em> inspection<\/h3>\n\n\n\n

C# or\/and\/not patterns can be useful to produce compact value checks without repeating the input value reference (value == 1 || value == 2 <\/code>vs. value is 1 or 2<\/code>). However, this syntax is still not as recognizable as good-old expressions like ||\/&&\/!<\/code>. Pattern priorities are not that clear at first, so it is easy to miss parentheses and introduce hard-to-find bugs.<\/p>\n\n\n\n

For example, the expression value is not 0 or -1 <\/code>compiles without any warnings. When the user\u2019s intention is to check the value for being not equal to both 0<\/code> or 1<\/code>, this check will evaluate to true with the value being equal to -1<\/code>. The correct pattern to use would be value is not (0 or -1)<\/code>.<\/p>\n\n\n\n

To help with situations like this, we introduced a new code analysis in version 2023.1 to warn you about “dead” checks inside complex patterns. Usually, those redundant “dead” pattern checks indicate a problem with a complex pattern.<\/p>\n\n\n\n

Convert to list pattern<\/em> context action<\/h3>\n\n\n\n

We\u2019re continuing to improve our support for C# 11 list patterns. With the new Convert to list pattern<\/em> context action, you can turn collection length checks into a list pattern syntax. It works in any context where a collection length check can be done.<\/p>\n\n\n\n\n\n\n\n

Editor<\/h2>\n\n\n\n

Option to specify the placement of pasted content<\/h3>\n\n\n\n

In Rider 2023.1, there\u2019s now a special setting that allows you to control the placement of pasted content. In Settings\/Preferences | Advanced Settings<\/em>, find the Editor<\/em> section and select the desired behavior for the Paste<\/em> action from the drop-down list.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Option to show whitespaces only in selected code<\/h3>\n\n\n\n

There\u2019s a new Selection<\/em> checkbox in Settings\/Preferences | Editor | General | Appearance | Show Whitespace <\/em>that allows you to configure this setting so that Rider shows whitespaces as small dots only when you select code.<\/p>\n\n\n\n

Text filters for unit test trees<\/h2>\n\n\n\n

Text search filters inside the Unit Tests <\/em>and Unit Test Coverage <\/em>tool windows are now taken into account when running tests using the toolbar\u2019s Run <\/em>buttons. Only the tests that satisfy the search criteria will remain listed and run.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

F# support<\/h2>\n\n\n\n

There’s a new quick-fix that generates missing pattern branches in a match expression.<\/p>\n\n\n\n\n\n\n\n

Notable fixes<\/h2>\n\n\n\n

Rider 2023.1 EAP 8 comes with a number of fixes for working with Unity projects:<\/p>\n\n\n\n