From d2e631c5ba2fb3542a99e9e471318a5dee367dbd Mon Sep 17 00:00:00 2001 From: asda488 <39116917+asda488@users.noreply.github.com> Date: Thu, 9 Nov 2023 10:25:03 +0000 Subject: [PATCH] Spelling correction index.md (#809) --- reactiveui/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reactiveui/index.md b/reactiveui/index.md index 14f30d25..c79b80d1 100644 --- a/reactiveui/index.md +++ b/reactiveui/index.md @@ -62,7 +62,7 @@ _layout: landing

Scalable & Testable

-

ReactiveUI copes gracefully as your application gets more complicated because of the Sytem.Reactive base (See the Introduction to Rx to learn more) on which ReactiveUI is built upon. These building blocks are particularly adept at expressing the relationship between a group of things that are changing. ReactiveUI is essentially a collection of extension methods that make expressing intention more convenient when implementing user interfaces. +

ReactiveUI copes gracefully as your application gets more complicated because of the System.Reactive base (See the Introduction to Rx to learn more) on which ReactiveUI is built upon. These building blocks are particularly adept at expressing the relationship between a group of things that are changing. ReactiveUI is essentially a collection of extension methods that make expressing intention more convenient when implementing user interfaces.

Waiting 3 seconds after receiving user input before instigating a request? Don't write a test that waits for 3 seconds - control time! Fast-forward 2.9 seconds, assert the request hasn't been sent, fast-forward another 0.1 seconds, and assert that it has. The functional idioms inherent in reactive programming lead to many other benefits including greater ease in testing your code & you will be able to assert the correctness of features and aspects of your application that you thought were impossible to test.