feat(profile): firestore profile shows up in firestore state (instead of firebase)

[goleary]

Do you want to request a feature or report a bug?
when I specify to use firestore for users profiles the data shows up under firebase in the store.

What is the current behavior?
i configured rrf to use firestore for the userprofile

const rrfProps = {
  firebase,
  config: {
    userProfile: "users",
    useFirestoreForProfile: true // Firestore for Profile instead of Realtime DB
  },
  dispatch: store.dispatch,
  createFirestoreInstance // <- needed if using firestore
};

yet it shows up inside the "firebase" section of the store, not the "firestore" section.

It looks like on data is actually store in firestore, but the way it is represented in my redux store is quite confusing.

What is the expected behavior?

I expected that the profile would show up inside the "firestore" section of the store.

[prescottprue]

Thanks for the suggestion!

Both auth and profile are within the firebase section since this library has been around since before Firestore. I agree that is somewhat unclear, but that will be a pretty breaking change for most, so this change would have to be in a next major version.

[goleary]

sure that makes sense, just hoping to prevent others from banging their heads on the table in the future as I did. Now that I understand how things are arranged I don't mind. Perhaps some additional clarity in the documentation would help in the interim.

[lesmo]

I think it could be proper to have it be part of both firebase and firestore keys because, well, the profiles collection would be expected to be seen under firestore anyways...