This branch may need to be split up...?

Summary

This PR is a proof-of-concept that would allow components to be connected to a mock workpad store.

There are a lot of parts to this PR:

Moving Storybook from .storybook to storybook

There are a lot of gotchas around typing and using eslint in a directory that begins in a .. It's been a constant pain, so I renamed the directory.

Custom Storybook Addon for Redux Actions

I wrote a custom addon for Storybook that not only provides a store to any redux component, but also patches the dispatch function to output the result of the action.

As a result, we can test our components as if they were in Canvas, and also see the results of any action.

Caveat: some of our reducers use Kibana or other services, and these blow up eventually. This is being mitigated by a project @crob611 is working on.

Applying a new component file structure for Redux components

I'm proposing a new structure for our components that is demonstrated here with asset, asset_manager and workpad_config:

- components
  - foo                       <- directory
    - index.ts                <- thin exporting index, (no redux)
    - foo.ts                  <- redux container
    - foo.component.tsx       <- react component
  - bar
    - index.ts
    - bar.ts
    - bar.component.tsx
    - bar_dep.ts              <- redux sub container
    - bar_dep.component.tsx   <- sub component

The exporting file would be:

export { Foo } from './foo';
export { Foo as FooComponent } from './foo.component';

Gotchas

• Some of our reducers rely on Kibana services to function. They blow up eventually, but still work.
• I'm concerned about storyshots choking under the weight of larger components, so I'm excluding stories named 'redux' from that test.
• This is beyond what kbn-storybook provides, and would require us to stay with our config, rather than migrate.