Sha256: e230049099fce5a42e6f03c2e79ee98f5a5fe599383ea621879c0117955972d4

Contents?: true

Size: 705 Bytes

Versions: 1

Compression:

Stored size: 705 Bytes

Contents

easy transforms, reactivity? When not to add a transform
net/http
stubbing
request error handling (timeouts...)

layers:
OAuth with refreshing (and on_refresh callback)
Redirect following
Caching
Batching
Page Crusher

api method on context to select context
complete method for quick layer (eg github gist star).
why not use stream, run, request in layers or in complete system.

HOOKS

stream flattening [[1,2,3]] => [1,2,3] (flat_map?)
stream::lazy; enumerable?

New relic instrumentation
Separate Parse/Render

move layer specific config to using istead of with
using [:render, :parse] => {
  template: 'person'
}

param :reload # transform { |r, param| r.query[param] = c[param] }
cache param blocks

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
commute-0.3.0.pre .todo