validatedObservable bug when the initial value is undefined

[thj-dk]

When the initial value of the validatedObservable is undefined, an observable is created with the validated property set to true. This is a problem, because one would expect the validatedObservable to be enabled when setting a future object.

[mikocot]

I think the problem still persists if undefined (or null) is passed as the intial value (common case if you initialize your viewmodel, but fill it with date asynchronously). The code:

ko.validatedObservable = function (initialValue, options) {
       if (!options && !kv.utils.isObject(initialValue)) {
        return ko.observable(initialValue).extend({ validatable: true });
    }
       [...]

returns before it subscribes to the observable and therefore ko.validation.group is never called on the object after it is updated. Which means the content of the validatedObservable is never validated if only it was initialized with undefined once. On the other side... just pass anything (ex. true) in options and the issue is gone..

[crissdev]

@mikocot See the following tests for more clarification https://github.com/Knockout-Contrib/Knockout-Validation/blob/2.0.3/test/api-tests.js#L714-L744
There's no way to tell, if the method is called with undefined, if you want groupping or not. So the default behaviour is correct but a hint from the consumer of the API is required (eg. options = {}) in order to achieve the desired functionality.