originally posted in:BungieNetPlatform
Nice, i did the same for Java, but, then when i tried to use it on my other own project i had issues, because i did it so easy to use that i was pretty much deciding the models to use in order that you don't have to worry about that, but, if you wanted to use certain DB frameworks or things like that require your models to follow some rules and then you end up having 2 models and things like that, so i just end up not releasing it :(
English
-
Edited by kodefuguru: 1/12/2016 6:11:40 PMThat criticism applies to my project as well. Here's how I would respond: 1. Many ORMs can handle plain objects just fine. 2. These models are DTOs. Map them to database entities instead of storing them. 3. O2O mapping is easy, but some frameworks make it even easier (e.g. [url=http://automapper.org]AutoMapper[/url] in the .NET world). 4. It's open source. You're welcome to fork my project and make all methods have a parameterized result like Task<TResult> MyMethod<TResult>(). Because of the way I designed the project, that last item is actually very simple. I won't put it in because the flexibility makes the library more difficult to use for the typical use case. [b]TLDR;[/b] release your project already :)