Gary Green

What does your dominar initialisation look like? On 26 Nov 2015 20:00, "Gary Hole" [email protected] wrote: > Can you setup a fiddle or repo I can check? > On 26...

I can't seem to replicate the issue, seems to work fine for me. http://jsfiddle.net/18yb3aja/

If you put `passes` as the third parameter to `.get` you need to make sure you don't return 200 for the `.fail` to be called when validation should fail.

I should probably add a `removeField` and general `destroy` function to dominar, along with a general config option for `ignoreMissingFields` ? What do you recon?

Just added a `destroy` method to dominar. Does that help with Meteor?

Yeah I haven't released new version yet. I'm going to hold off until I get a chance to release validatorjs 2.0. I was thinking when you remove the elements (or...

I'm definitely interested in supporting, just need to find a decent way of doing it. :smile: When the view is rendered in Meteor `onRendered` could you `.destroy` and then re-initialize...

How does Meteor recommend to handle initializing e.g. date pickers, custom selects, star ratings, wysiwyg editors, sortable elements, etc when the view is constantly being re-rendered / changed with new...

What I'm trying to suggest is when you know your view has been re-rendered (thru 'done rendered' events, or whatever) THEN do `dominar.destroy()` and `var dominar = new Dominar(..., ...);`...

In all honesty, I think that's a pretty stupid design by Meteor. How come you can't tell when a control is updated? I really don't see how on earth you...