[data-explorer][m]: refactored to work with data explorer concept.

[anuveyatsu]

• update props of the App container
• update logic behind App container
• update fixtures to do dev with cosmos
• update unit tests

[starsinmypockets]

The implementation looks good to me.

See my note about exporting the App component from the index file. I'm open to discuss.

[starsinmypockets]

I don't think we need to do this here. We can check this using cosmos or unit tests.

[starsinmypockets]

Same. I think all of this can go.

[starsinmypockets]

I don't think we need this either. I think we just need:

export default App

so that we can load this in the parent app (Data Explorer, for instance) like this:

import FilterUI from './components/FilterUI'
import DataView from 'datapackage-views'
import DataViewBuilder from './components/DataViewBuilder'
import { filterUIAction, fetchDataAction, dataViewBuilderAction } from './actions/';

export const App = props => {
  
  return (
    <div className="text-center ml-6">
      <header>
        <div className="container">
          <h1 className="text-3xl">Data Explorer</h1>
        </div>
      </header>
      <div className="container py-6 bg-pink-100">
        <div className="">
          <FilterUI {...props} />
        </div>
      </div>
      <div className="container flex py-6 bg-yellow-100">
        <div className="w-3/4 p-4 mr-4 overflow-x-auto">
          <DataView {...props} />
        </div>
        <div className="w-1/4 p-4 mr-4 bg-green-100">
          <DataViewBuilder {...props} />
        </div>
      </div>
     </div>
  )
}

We might then need to add a wrapper that includes this App for Datahub.io or Preview pages, but I think the module should just export the component.

[anuveyatsu]

@starsinmypockets before merging this we need to make sure that other projects won't break, e.g., this library is now being used for several projects.