RWOverdijk
commented
8 years ago Small update, I know now I can use the validate attribute to define the property. I'd still prefer a different approach, but it works for me.
On the subject of nested validations I am curious how I should specify something that states that the property is an object, of which I wish to validate specific properties.
export default class Article extends Entity {
@ensure(it => it.isNotEmpty().hasLengthBetween(3, 20))
name = null;
// This is an object. I wish to validate id and foo, too. I don't know how to apply rules to these.
user = {id: 1, username: 'foo'};
}
plwalters
Hello,
I'm trying to use this module like this: https://gist.github.com/RWOverdijk/fd75b26c0a6ac3683dbe
What I'm trying to do, is contain validation within models. However, what happens, is that validation uses the names of the properties (such as name, address, postcode) as key.
Validation does work, but visual feedback doesn't. The reason for this, is that the strategies look for elements that have the property name as value for one of the following attributes:
'validate', 'value.bind', 'value.two-way'.In my case, this won't work, because the model is referenced using
location.name, which isn'tlocation.How can I work around, or fix, this in this module?