Add FAQ section in the docs

[jvanbruegge]

A few questions keep popping up from time to time, most of the time related to snabbdom usage. Two current examples are #808 and #807 .
I think we should add a section in the docs where we can provide solutions for those common problems.
Problems to include:

• hooking into the element creation/update/deletion (Best integration strategy with CSS lib? #807)
• Using props for attrs that change (except for svg) (Inconsistencies in form input element DOM updates  #808)
• Execute code when DOM is loaded (Stackoverflow)
• Lenses with makeCollection (Stackoverflow)

[staltz]

Agreed! We could put it as a "chapter" in the Guide, after "Drivers" chapter.

[staltz]

#810

[jvanbruegge]

Added a few FAQ entry to the top post (to be extended)

[jvanbruegge]

Added lenses with makeCollection

[staltz]

Where are you adding these things?

[jvanbruegge]

Oh, just to the top comment, to keep track of them. I havent started (or have the time to start) a proper FAQ yet

[jopek]

TypeScript Problem

HTTP.select('XX').flatten() returns a MemoryStream<Response> & ResponseStream type. when assigning it to a Stream one gets a typescript error:

Type 'MemoryStream<Response> & ResponseStream' is not assignable to type 'Stream<Response>'.
  Types of property '_prod' are incompatible.
    Type 'import("/Users/alex/dev/learn/cyclejs/playground/node_modules/xstream/index").InternalProducer<import("/Users/alex/dev/learn/cyclejs/playground/node_modules/@cycle/http/lib/cjs/interfaces").Response>' is not assignable to type 'import("/Users/alex/dev/learn/cyclejs/playground/node_modules/xstream/index").InternalProducer<Response>'.
      Type 'import("/Users/alex/dev/learn/cyclejs/playground/node_modules/@cycle/http/lib/cjs/interfaces").Response' is not assignable to type 'Response'.
        Property 'headers' is missing in type 'Response'.

TypeScript probably thinks you mean this Response https://developer.mozilla.org/en-US/docs/Web/API/Response

Solution

import { Response } from '@cycle/http';

[bemayr]

Great idea, when showing cycle.js to programmers I often experienced that resetting state (e.g. reset the Counter Example to 0) requires a different thinking. Maybe we could add this as well.

[jvanbruegge]

I am closing this in favor of #851