Listener not updated if props change about react-firestore HOT 3 CLOSED

@damonbauer I had some trouble with that as well, but was able to get it to work using:

<Route
  path="/leagues/:id"
  render={props => (
    <FirestoreDocument
      path={"/leagues/" + props.match.params.id}
      render={({ isLoading, data }) => {
        return isLoading ? (
          <Loading />
        ) : (
          <League league={data} {...props} {...this.props} />
        );
      }}
    />
  )}
/>

I believe this is working because by using the render option for Route the FirestoreDocument is getting completely unmounted/remounted each time the route fires.

from react-firestore.

Another use case:

I've got a container component that mounts a FirestoreDocument and renders a stateless component with the data received from FirestoreDocument.

Using react-router, I have a link to a route that mounts said container. If I'm already on a route that has the container mounted, I never getting a request for new data. Here's an example:

While at route: example.com/item/itemID1, I'm mounting this:

<FirestoreDocument
  path={`items/${id}`} // `id` will be "itemID1"
  render={({ isLoading, data }) =>
    isLoading ? <Loading /> : <ItemDetail {...data} />
  }
/>

If I click a link to example.com/item/itemID2, the path prop in the FirestoreDocument does get updated with itemID2, but it does not kick off a request to fetch that data; nothing changes, so my ItemDetail component never re-renders with any new data.

from react-firestore.

Closed by #10

from react-firestore.