feat: header extraction improvement (close: #238)

[ulivz]

Summary

Fixed: #238
Test Header:

## `How` [It](/app/) <Works> **app** _italic_ *italic*

Snapshot

Before

After

[ycmjason]

The checking of the processors.length seems unnecessary. Perhaps something like this?

const compose = (...processors) => {
  return processors.reduce((prev, next) => {
    return (...args) => next(prev(...args))
  }, x => x)
}

Or

const compose = (...processors) => {
  return [
    x => x,
    ...processors
  ].reduce((prev, next) => {
    return (...args) => next(prev(...args))
  })
}

[ulivz]

Hmmm? Are you telling me how to write code?

Code should be as easy as possible to understand, don't always think about drag racing.

If you expect me to make a change, first give redux a PR.

[yyx990803]

@ulivz I also prefer easier to read code, but this is open source and @ycmjason is just offering what he thinks might be better code. He is not telling you how to write code and you don't have to be combative about this.

[ulivz]

@yyx990803 Yes, I should say convincing reasons instead of arguing for it.

@ycmjason I'm terribly sorry about my recklessness, and I liked the style what you said above, but, after a long time, I found I always need to think back to what parameters of reduce's callback needs to accept. Until one day I read the source code of Redux, I found it's easier to undestand. so I'd like this style.

[ycmjason]

Just one comment, LGTM otherwise.

[ycmjason]

Just curious, did you miss return here? And the next line?

[ulivz]

Nice! Thanks! fixed at a8c6959