Aspnetcore: .razor parsing forces code blocks, even in functions block

Created on 22 Apr 2019 · 7Comments · Source: dotnet/aspnetcore

Describe the bug

The compiler does not allow "single-statement control flow statements" In the "cshtml" part of a .razor file. I understand that is required, but currently it also enforces this rule in the "@functions" block. My understanding was that in the @functions block any normal c# syntax can be used.

To Reproduce

"dotnet new blazorserverside"
Edit the "components.razor" file and replace the "IncrementCount" function with:

 void IncrementCount()
    {
        if (true)
        currentCount++;
    }

Expected behavior

It should not give a compile time syntax error

Done area-blazor bug

Source

tn-5

👍6 👎1

All 7 comments

I would also like to support the code without using {}

cores-system on 22 Apr 2019

We are able to reproduce this.

danroth27 on 23 Apr 2019

(This appears to be a regression in preview4 compared to preview3.)

chucker on 23 Apr 2019

Using VS 2019 16.1 Preview 2 with 3.0.0 Preview 4

vertonghenb on 24 Apr 2019

I am facing the same issue using VS2019 16.1 Preview 2 and .NET Core 3.0.0-preview4.

https://gist.github.com/MaherJendoubi/d6e15a1da422dc33cb8b4d27916a5fe5

Razor engine cannot parse the lambda expression at line number 51:

receiveClient.RegisterMessageHandler(
async (message, cancellationToken) => await receiveClient.CompleteAsync(message.SystemProperties.LockToken),
messageHandlerOptions);