Allow defining default values for query filters

[gcirne]

For example, I would like to specify a default value of 10 for the limit filter of a particular model. In situations where no explicit limit is given, then the default value of 10 should be used.

[fabien]

@gcirne see #172 - this is for hasMany relations, but perhaps we can do something similar for what you're requesting. @raymondfeng thoughts?

[gcirne]

Sure, that sounds good.

Guilherme Machado Cirne
[email protected]

On Fri, Jul 11, 2014 at 2:06 PM, Fabien Franzen [email protected]
wrote:

@gcirne https://github.com/gcirne see #172
#172 -
this is for hasMany relations, but perhaps we can do something similar for
what you're requesting. @raymondfeng https://github.com/raymondfeng
thoughts?

—
Reply to this email directly or view it on GitHub
#168 (comment)
.

[raymondfeng]

Maybe we should try to unify everything under scope?

1. scope defines some sort of constrained connection to other models or the declaring model itself.
2. scope has the following properties:
   • name
   • sourceModel
   • targetModel
   • predefined query filter (can be static and/or dynamic)
   • predefined related properties (can be static and/or dynamic)
3. For a model, we can define a default scope
4. scopes can be chained (such as User.vips.active)

[raymondfeng]

My ambition for a LoopBack model will be:

1. A model has a list of managed properties and optional open properties
2. A model has a list of connections to other models or services
   • relations
   • scopes
   • custom methods
3. A model can have extra metadata for persistence/transfer/remoting
4. A model can have behaviors (methods) mixed in from connectors or custom code
5. The model properties and connections form a model graph
6. The model graph allows you to read/write local states (properties) and connected states (connections)
7. The model graph allows you to navigate following connections
8. The model graph has the ability to pick and choose what information to be selected
   • select a list of instances
   • select a list of properties for a given instance
   • select a list of connected instances or data
   • embed the data or embed the links

[raymondfeng]

The defaultScope should support your use case now.