ducky/web

Paddy 2015-05-31 Parent:99a43a6d1d30

6:a641906b8267 Go to Latest

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™.

Download raw file
View source Diff to previous Annotate
History
1 import React from 'react'
2
3 export default React.createClass({
4 displayName: 'ErrorPage',
5
6 propTypes: {
7 title: React.PropTypes.string,
8 message: React.PropTypes.string.isRequired
9 },
10
11 render () {
12 const {title, message} = this.props
13 return (
14 <div>
15 <h1>{title}</h1>
16 <p>{message}</p>
17 </div>
18 )
19 }
20 })