Open thrawnarn opened 6 years ago
It's a design decision from the original PetaPoco. I'd like to be pragmatic and expose it if it's useful, but I also want the code base to be consistent and "make sense", and currently nothing under the AsyncPoco.Internal
namespace is public. I generally put faith in those original decisions unless I'm convinced otherwise. Can you provide details on what you want to use from PocoData? Maybe you can convince me. :)
Is there a reason why PocoData isn't public? It would be great to have it public to be able to access the same information about the models as AsyncPoco. I usually writes a layer above my poco to be able to reuse code more efficiently...