- Users want to compose reducer tree across modules
- Idea of a single reducer function makes it difficult for the library to dynamically augment the shape of the state tree
- Turning control over to the library to build the root reducer limits the use of meta-reducers
- Feature modules may inadvertently collide with the state of the root module
- Library authors may want to leverage @ngrx/store in their projects and provide an easy way
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/* | |
Sample output: | |
> gradle test ruby-1.9.3-p194 testing_with_gradle 9179829 ✗ | |
... | |
:test | |
Results: SUCCESS (84 tests, 74 successes, 0 failures, 10 skipped) | |
*/ | |
test { | |
testLogging { |