ducky/web: a641906b8267 bin/dev-server

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 #!/usr/bin/env node

3 var fs = require('fs')

4 var path = require('path')

5 var webpack = require('webpack')

6 var WebpackDevServer = require('webpack-dev-server')

7 var argv = require('minimist')(process.argv.slice(2))

8 var findRoot = require('find-root')

9 var rootFolder = findRoot(process.env.PWD)

11 var configfile = '';

13 // get config

14 if (argv.config) {

15 configfile = path.resolve(argv.config)

16 } else {

17 configfile = path.resolve(path.join(rootFolder, 'webpack.config.js'))

18 }

19 argv.config = require(configfile);

21 // run it

22 new WebpackDevServer(webpack(argv.config), {

23 historyApiFallback: true,

24 hot: true,

25 publicPath: argv.config.output.publicPath,

26 }).listen(argv.config.port, argv.config.host, function (err, result) {

27 if (err) {

28 console.log(err)

29 }

30 console.log('development server running at: http://' + argv.config.host + ':' + argv.config.port)

31 })

ducky/web

ducky/web/bin/dev-server