MikeRyanDev

@ngrx/store v3

Problems:

• 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

peterbsmyth

Making chained API Calls using @ngrx/Effects

Purpose

This recipe is useful for cooking up chained API calls as a result of a single action.

Description

In the below example, a single action called POST_REPO is dispatched and it's intention is to create a new repostiory on GitHub then update the README with new data after it is created.
For this to happen there are 4 API calls necessary to the GitHub API:

1. POST a new repostiry
2. GET the master branch of the new repository
3. GET the files on the master branch

rcknr

function md5(inputString) {
  return Utilities.computeDigest(Utilities.DigestAlgorithm.MD5, inputString)
    .reduce((output, byte) => output + (byte & 255).toString(16).padStart(2, '0'), '');
}