GummyA

@hoquocdat We're happy to showcase your company on our web site! Optionally, you can also send us 2-3 sentences about your LoopBack usage that we can use it in [https://loopback.io/what-our-users-say.html](https://loopback.io/what-our-users-say.html)...

Discussion: From @raymondfeng: do we want to split the queries for users, or just have a limit amount of queries(i.e throws err msg if they exceed the limit)? Any thoughts?...

I was considering this use case: Lots of shopping websites use `Load More` button(or scroll down) to load more items. This kind of button/function only sends a certain amount of...

https://github.com/strongloop/loopback-connector-postgresql/pull/404 might be related to this issue

I was checking filters these days. `order` filter works well with API Explorer when I tested it. Both work: ``` { "order": [ "number ASC" ] } or { "order":...

Agree, `"order ASC"` is not intuitive enough. Maybe we can have a layer to convert `"order": "ASC"` to `"order ASC"`, thoughts? @raymondfeng

@lakshmansai1980 If you'd like to filter some properties in the object `location`, you will need to include `location` in the result. i.e set the whole object to true in the...

Current status (in MongoDB): - for LB3, can use nested fields to fetch data from database, **but** it fails to create an instance with nested fields. - for LB4, juggler...

https://github.com/strongloop/loopback-datasource-juggler/blob/master/lib/dao.js#L207

@lakshmansai1980 what I've verified is that the mongodb connector itself is able to fetch correct data from the db with queries, `userRepo.find({where: {address.city:'Toronto'}, fields:{'address.city': true}})` for example. i.e [`execute`](https://github.com/strongloop/loopback-connector-mongodb/blob/master/lib/mongodb.js#L467) method...