model.set: validate only when silent = false, why?

[wolfgang-adamec]

Hello!
With model.set I want to change my model, but I do not want events triggered, so I call "model.set" with silent=true.
But with this the validate function is not called.
Why?
Thanks alot
Wolfgang

current Backbone.js source code (0.5.3)
( set : function(key, value, options) {
...
// Run validation.
if (!options.silent && this.validate && !this._performValidation(attrs, options)) return false;)

[jashkenas]

Because the point of silent changes is that you're allowed to twiddle with the internal state of your model, temporarily, without actually making a change. Later, when the attribute actually changes, the validation runs and events are emitted. It wouldn't make sense to emit an error event when making a silent change.

[gudnm]

Jeremy, you are right, however this behavior makes possible to initialize an object with invalid parameter, which later throws off validate() when making valid changes. See http://stackoverflow.com/questions/8915288/backbone-model-validation or an example below -

> var me = new Person({'name': 'Ivan Vashchenko', age: -29});
undefined
> me.toJSON();
Object {name: "Ivan Vashchenko", age: -29, occupation: "farmer"}
> me.on('invalid', function(model, error) {
>   console.log(error);
> });
child {cid: "c2", attributes: Object, _changing: false, _previousAttributes: Object, changed: Object…}  
> me.save('name', 'My alter ego');
Person's age can not be negative.
false

It seems to me a validation could be useful on initialization as well...