ducky/web

Paddy 2015-05-31 Parent:99a43a6d1d30

6:a641906b8267 Go to Latest

ducky/web/src/styles/hero.scss

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â„¢.

History
1 @import 'bourbon';
2 @import "neat";
3 @import "base/base";
5 $hero-background: #40526b;
6 $hero-color: white;
8 .hero {
9 background-color: $hero-background;
10 background-repeat: no-repeat;
11 background-position: top;
12 background-size: cover;
14 img.hero-logo {
15 height: 80px;
16 margin-bottom: 1em;
17 }
18 .hero-inner {
19 @include outer-container;
20 @include clearfix;
21 padding: 3em 3em 0 3em;
22 margin: auto;
23 text-align: center;
24 color: $hero-color;
26 .hero-copy {
27 text-align: center;
29 h1 {
30 font-size: 2.5em;
31 margin-bottom: .2em;
32 }
34 p {
35 margin: auto;
36 margin-bottom: 3em;
37 font-weight: 200;
38 font-size: 1.25em;
39 }
40 }
41 }
42 }