(Tutorial) ReactiveCommands in ViewModel constructor don't work

[Rhywun]

I am following the tutorial on macOS 10.15.5 and .NET Core 3.0. All is well until the final page which adds the functionality for the OK and Cancel buttons in the constructor of the AddItemViewModel class. There are two problems upon running:

1. The "OK" button remains disabled when I enter text in the Description field.
2. The "Cancel" button results in a blank window instead of returning to the TodoListView.

Repro here.

Thanks

[FoggyFinder]

1. You wrote Command="{Binding OK}" instead of Command="{Binding Ok}"

https://github.com/Rhywun/avalonia-todo/blob/master/Views/AddItemView.xaml#L13

2. You didn't initialize List property

Content = new TodoListViewModel(db.GetItems());

while it should be

Content = List = new TodoListViewModel(db.GetItems());

https://github.com/Rhywun/avalonia-todo/blob/master/ViewModels/MainWindowViewModel.cs#L14

[Rhywun]

Thank you!! Everything works now.

Ugh I remember typing in your second line and I thought it was a misprint :)
That kind of double assignment rubs me the wrong way.

Might I suggest providing the source code for the tutorial on the website? I didn't find it in the framework's samples/ directory either. It might help others by providing a way to diff any changes.

[rstm-sf]

Hello! Link is already exist:

You can find the code for the completed application here.
https://avaloniaui.net/docs/tutorial/

[Rhywun]

Great, thanks! I missed it.

Closing

[FoggyFinder]

Thank you!! Everything works now.

Happy to help. Btw, there are also places where you can ask Qs about Avalonia:

• Chat in gitter: https://gitter.im/AvaloniaUI/Avalonia

• Chat in discord: https://aka.ms/dotnet-discord

• Ask on SO: avalonia

• Ask on TopAnswers: C#

• Maybe even on recently created CoDidact.Software Development

First two are probably preferable since they have "official" (mention in ReadMe) support.

I do think it would better than raise issues especially in case of something simple. Avalonia has reached the good shape and answering questions is area where community can help easily.

To emphasize: this is only my personal position and maintainers may think differently.

My arguments are the following:

• Questions distract from working on fixing bugs, implementing new features etc.

• It might be annoying for watchers to receive notifications about something simple like "WebView ??" again and again.

• Sometimes issues don't recive any response anyway

• and even when the answer is provided issue is not always marked as "closed" therefore reports about possibly crucial bugs go down and down.

[Rhywun]

"Chat" is not my favorite format but I will take it under consideration. Thanks

PS. The progress since I first looked at Avalonia a couple years ago is fantastic. Much appreciated.