Errors are displayed at the first loading form / How to use a class context in validation methods

[ermouth]

Errors are displayed at the first loading form / How to use a class context in validation methods

[ermouth]

Thanks for your question, Camel. I think I need to update reference to accent how this works inside $.my functions.

$.my apps intended to be more or less self-contained – to build systems were every app is a single json doc without (or with minimal set) of external dependencies. To ensure consistent runtime environment for every manifest fn, each init, bind, check, css, style and manifest function of given manifest receives manifest itself as this object.

Out-of-syntax user functions, defined at a first level of given manifest tree, also are bound to the manifest via this when app starts.

So nearly any fn called inside manifest is bound to manifest itself – you may think about manifest as if it‘s a sort of class definition.

To fix you particular case you can write this.validator.checkNotEmpty.bind(this) in the manifest – it binds function to this explicitly. I think it can help.

Thanks again for you deep-level question!

[ermouth]

For question №1 – there are several approaches to achieve this kind of behavior.

1. You can explicitly define a set of events $.my listens for the control. For example events:"blur.my" set for <textarea> ensures that validator fires after field left focus. It sometimes means that user finished with this field.
2. You can do it right in the way you do it now – but keeping allowEmptyField as property of manifest instance. So you check function is able to set/retrieve its value from this.allowEmptyField during runtime.
3. You can use regexps like /^(|\d{3,5})$/ – it allows 3-5 digits, but stays dumb if string is empty. In this case you can make additional proxy <div> that watches all your fields (watch:"#f1,#f2,f3") and tells user something like ‘You must write something in fields F1, F2, F3’.

[camelaissani]

I had guessed your answer ;-)
Thank you for your help