One of the most common issues when starting developing with ReactiveX is the issue that "nothing happens". There are several ways to avoid this, mostly by following the same development principles as any other piece of code:
- Write small parts of code and test them with unit tests. Whenever possible, follow test-driven development (TDD). It feels like a waste of time in the beginning, but from my experience it saves time as soon as the first development release is delivered.
- Develop the application step-by-step, with something that executes as early as possible. The initial implementation will be full of stubs, but they are already doing something. With each feature being implemented one after an other, finding an issue is easier.
Following these simple principles, you may still not make any progress. In this case, using the do_action...
