ducky/web

Paddy 2015-05-31 Parent:99a43a6d1d30 Child:275a83e4c02e

6:a641906b8267 Go to Latest

ducky/web/src/main.js

Enable catch-all in our ValidationError component. We're doing this an ugly, hacky way. But it works, and right now, that's what counts. To match our params/fields/headers properties on the ValidationError component, we're going to add the notParams/notFields/notHeaders properties--they match any error _not_ targeting those params/fields/headers. Basically, "any error that wouldn't be caught by these filters". Which is an ugly, but workable, solution for a catch-all ValidationError--just tell it to catch anything but the params/fields/headers that are being handled by the other ValidationErrors. Our implementation of this in the RegisterPage component validates (ha!) that it's at least workable model, if not overly pretty. Also, I anticipate some human error bugs in the future, where one of the field-specific ValidationErrors gets updated and the catch-all ValidationError does not. But whatever. For now, this is Good Enough™.

Download raw file

View source Diff to previous Annotate

1 import app from 'ampersand-app'

2 import Router from './router'

3 import Profiles from './models/profiles'

4 import Me from './models/me'

5 import normalize from 'normalize.css/normalize.css'

6 import styles from './styles/main.scss'

8 window.app = app.extend({

9 init () {

10 this.profiles = new Profiles()

11 this.me = new Me()

12 this.router = new Router()

13 this.router.history.start({ pushState: true })

17 app.init()