Universal search demo pt 1: google drive.

[adamberenzweig]

Sending a bit early because I just saw you have some overlap in #46 .

Looks like we can manage it without using the old python backend at all. Added some new scope to firebase auth. The server fetches the credentials (stored during client registration) and sticks them into the request context, available to send to the Google Drive API.

Notes:

• We're now passing the whole User object (retrieved from FirebaseUserStore) through context so we can use credentials.
• So far I haven't used the SearchResult schema; I'm still unsure whether we need a separate operation for items() vs search().

[adamberenzweig]

Rich, what should happen when someone clicks on a search result that corresponds to an external link (Document)? In the current design, there's no way to render a detail page, because the transient item ID doesn't exist in the store. I can link to the external URL, but that's confusing UX.

I think we've reached the limit of what we can do with generic item rendering in lists. I started tinkering w/ type-specific ListItem components. I can keep going down that road if it seems right.

[richburdon]

Re comments above.

1). I think the main concern is to normalize ListItem rendering and dispatch the TypeRegistry for custom fields (or column sections).

2). OK with me to merge after you've taken a look at this: https://docs.google.com/document/d/1qMwaBb8jcip1zZipvFIM5SZDDE07ZL5Lpz0UtM1dH-I/edit#