Search: wrap summary data to Search component

[zlatanpham]

WHAT:
I am using the Search component to build the interface for #102 but the UI requires data like totalResults, q.original, etc and I have to use Consumer to get these data.

WHY:
It's cumbersome to write nested render-prop components since we can do an update to use just Search only.

HOW:
Get all the needed data from pipeline methods like getResults or getResponse and inject those to summary prop and pass to render prop function.

[benhinchley]

The following two lines have the potential to override each other, q in Query values will get overridden by q in responseValues if autocomplete is running. It might be worth having a queryValues, and responseValues key in the SummaryInterface.

...mapToObject(response.getQueryValues()),
...mapToObject(response.getValues()),

[zlatanpham]

@benhinchley I've updated the code as your suggestion and also explicitly made the keys of queryValues,.. visible rather than using [key: string]: number | string. Not sure it's ok to you because I guess those properties would be permanent.

[benhinchley]

Hey @zlatanpham the values for a query, can be anything as a user can customise the variables needed for their pipeline. So the correct type for these objects is actually { [k:string]: string | number }

[zlatanpham]

updated!