Multiple Flow errors resulting from possibility of null object IDs

[benknight]

I just upgraded to a version of this library that has Flow types, and now Flow is reporting errors just about anywhere I reference the "id", for example of in DocumentSnapshot, Path, CollectionReference, and DocumentReference.

Solving these errors requires adding existence checks everywhere in my application that accesses an id property, which seems unnecessary and cumbersome. Are there really common/valid cases where an objects id would be null? Basically I'm not seeing a need for the | null part of the type definition.

[Ehesp]

Thanks for flagging - I'll look into this one, from a quick look I think you may be correct but will let you know for sure.

[Salakar]

@benknight thanks for the report, have swapped these to be string only as you're right. Will land in v5.2.0. Sorry for the delay.