Andrey G.

yep, caught self on same thoughts - hard to understand internals. Separated sources would be more nice. I read about private, but not sure that's enough reason.

@tommikaikkonen First of all, thanks for library, it helps a lot in my projects (no need to reinvent wheel, though I was on that way). I'm using it in my...

Not sure that **democratic** way is working in development, especially in open source (but I've never been in such projects). I'm sure that we need a person (maybe few) that...

What do you mean denormalization API in our case?! On 3 Jun 2017, 10:36 +0300, Neal van der Valk , wrote: > @tiii +1 for the documentation and api for...

Well, we are using this library a lot in our application and I must say, that your case is very limited. E.g. You need only subset of relations where some...

@nealoke in our case we created and using next selectors: ```js createSelector, //unified selector, that creates ORM selector or selector from reselect createRecordSelector, //to select single record with query info...

@tiii separate library, because I'm not sure that it fits here (E.g. in our case we use multi-schema ORM, where some schemas are same, but has differ keys at global...

I don't use it, so probably not. Maybe someone else On 11 Jun 2017, 15:21 +0300, Neal van der Valk , wrote: > @plandem Are you also planning to update...

@NathanBWaters agree, that someday we need to tune performance :)

@Aryk yep, if explicitly then you will have to define on both models and in case of custom **through** model it can be verbose :) but...at least no surprises :)