Open to making the file transport pluggable?

[chmac]

Open to making the file transport pluggable?

[chmac]

I forked the repo and started some experiments. On reflection, I don't think this approach makes sense. There's so much formatting and so on in the transport, that I guess it makes more sense to simply create my own transport in my app. I might also publish that as a package, not sure yet.

Expo doesn't have an appendFile, so I'll likely shard the files by date and so on as well.

[alessandro-bottamedi]

Thanks for the appreciation :), I don't really know how expo-fs works but i think the best idea is to create a new transport, it's the easiest way to do it.

If you create your transport with expo-fs then we can integrate it in the package

[chmac]

@alessandro-bottamedi I tried this approach this morning, just pushed the branch if you want to check it out. The approach worked locally. But the dependency on expo-file-system is invisible, which I'm not quite sure about. I guess it would make sense to publish transports which have dependencies as their own packages, so they're tracked separately.

I didn't end up using expo-fs as it's just another layer of abstraction which wasn't necessary in this case. If you want to add the expoFileSystem transport into core, the code I pushed might work.

I also added a prettier configuration and some other stuff, but I haven't pushed any of that. I'm leaning more and more towards my own app specific transport.