ducky/web: a641906b8267 src/styles/base/

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

1 #{$all-button-inputs},

2 button {

3 @include appearance(none);

4 -webkit-font-smoothing: antialiased;

5 background-color: $action-color;

6 border-radius: $base-border-radius;

7 border: none;

8 color: #fff;

9 cursor: pointer;

10 display: inline-block;

11 font-family: $base-font-family;

12 font-size: $base-font-size;

13 font-weight: 600;

14 line-height: 1;

15 padding: 0.75em 1em;

16 text-decoration: none;

17 user-select: none;

18 vertical-align: middle;

19 white-space: nowrap;

21 &:hover,

22 &:focus {

23 background-color: darken($action-color, 15%);

24 color: #fff;

25 }

27 &:disabled {

28 cursor: not-allowed;

29 opacity: 0.5;

30 }

31 }

ducky/web

ducky/web/src/styles/base/_buttons.scss