ducky/web

Paddy 2015-05-31 Parent:99a43a6d1d30

6:a641906b8267 Go to Latest

ducky/web/src/styles/base/_tables.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 table {
2 @include font-feature-settings("kern", "liga", "tnum");
3 border-collapse: collapse;
4 margin: $small-spacing 0;
5 table-layout: fixed;
6 width: 100%;
7 }
9 th {
10 border-bottom: 1px solid darken($base-border-color, 15%);
11 font-weight: 600;
12 padding: $small-spacing 0;
13 text-align: left;
14 }
16 td {
17 border-bottom: $base-border;
18 padding: $small-spacing 0;
19 }
21 tr,
22 td,
23 th {
24 vertical-align: middle;
25 }