Slavrix

This is exactly what I ended up doing for now. I still needed to play around with the padding and width to make it look good. and the table header...

An issue with the current backup form is that it is currently JSON.stringifying all of the data in the document. This causes issues with keeping the dataType of each field....

doesn't seem to be a way to just add a document using the above format. However, looking through the firestore package. `@google-cloud/firestore/src/doucments.js`on line 402 we have a method that is...

Reference data types need more work still though. the reference can then be reimported through `let reference_to_import = firebase.doc(the_saved_reference_string)` the depth of the string needs to be checked through and...

its janky but it works ``` let toRemove = 'projects/'+firestore._referencePath._projectId+'/databases/'+firestore._referencePath._databaseId+'/documents/'; let toFind = proto.referenceValue.replace(toRemove, ''); console.log(toFind); return firestore.doc(toFind); ``` in the referenceValue section of the switch

Hopefully, this helps if you guys haven't already got restoring working better. there is probably a better way to do it, but this works for me for now.

Yea that switch itself came from the official node firebase package with just the one tweak for reference files. I figured if that's how they are doing it it's probably...

@ardatan id love to assist with getting this package updated, but i dont know where to start.

Ok I've been playing around and I found that my `ng serve` was working locally. I also found that if I did `ng build --watch` and then served the result...

And this is back again with an angular 13/ionic 6 project with meteor 2.5.1