Sergii Kalashnyk

`offset` is something that is not recommended to use by google - https://cloud.google.com/firestore/docs/best-practices#read_and_write_operations > Do not use offsets. Instead, use cursors. Using an offset only avoids returning the skipped documents...

@wovalle, could you provide more details? I tried to use `@google-cloud/firestore` (instead of `firebase-admin`) and fireorm worked fine.

@wovalle, it seems that he need firestore's `extractTFromDocSnap(docSnap)` method. Now it's repository class-member private func. @theochampion, you can use `plainToClass(YouModelClass, docSnap.data())` since `fireorm` also uses it to serialize plain docs...

@GitTom , it's possible to have several definitions, something like this: ``` class Foo { id: string = null; name: string; age: number; constructor(); constructor(name: string); constructor(age: number); constructor(nameOrAge?:string|number) {...

> @skalashnyk Interesting. I guess that is a Typescript attempt to work around the limitation. Seems a bit awkward though, and I prefer not to stray that far from JS...

This error is thrown by firestore sdk ``` import * as admin from 'firebase-admin'; class Hello { } admin.firestore() .collection('foo') .doc('test_1') .set({ prop: new Hello() }) .then(console.log) .catch(console.error); ``` Output:...