ducky/web
ducky/web/src/pages/message.jsx
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™.
| paddy@0 | 1 import React from 'react' |
| paddy@0 | 2 |
| paddy@0 | 3 export default React.createClass({ |
| paddy@0 | 4 displayName: 'ErrorPage', |
| paddy@0 | 5 |
| paddy@0 | 6 propTypes: { |
| paddy@0 | 7 title: React.PropTypes.string, |
| paddy@0 | 8 message: React.PropTypes.string.isRequired |
| paddy@0 | 9 }, |
| paddy@0 | 10 |
| paddy@0 | 11 render () { |
| paddy@0 | 12 const {title, message} = this.props |
| paddy@0 | 13 return ( |
| paddy@0 | 14 <div> |
| paddy@0 | 15 <h1>{title}</h1> |
| paddy@0 | 16 <p>{message}</p> |
| paddy@0 | 17 </div> |
| paddy@0 | 18 ) |
| paddy@0 | 19 } |
| paddy@0 | 20 }) |