Phil Freo

I haven't upgraded my app to the refactored (0.12+) Backbone-Forms yet, so no, but when I do I'll be sure to post my updated version. The main thing is the...

I was trying to do the exact same thing (for the exact same reason of bootstrap input add-ons)

Rather than relying on model toJSON (sometimes which doesn't include every attribute if you don't want the server to see it) I'd rather put an extra options/values in the schema,...

If I'm understanding what you mean by `data`, I don't think that's where it always belongs, since the data isn't always specific per model. It's usually specific per field. But...

There's not really a good way to know if an ID should always be numeric or not, and "sometimes" returning an int vs string seems like a bad idea to...

From the README: > There are 2 levels of validation: schema validators and the regular built-in Backbone model validation. Backbone Forms will run both when form.validate() is called. Calling form.commit()...

One idea is to move `slug` validation to the Backbone model then. Or have a selective backbone-forms validator that only gets triggered when a certain criteria (final submission) is true.

#363 is related and also seems like a good idea (I always thought it was strange to not set `this.value` in `setValue`) --- however my case here is even simpler...

@tamagokun what you're describing is _not_ re-rendering a Backbone Form. It's destroying the form and re-creating a new one.

The idea of (recent) versions of Backbone-Forms is that a Form is just a regular view that could be extended, keep its own state, etc. so there are cases where...