| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
these now have their own top-level config attribute which is essentially a
shorthand for setting one that's deeper nested.
|
|
|
|
|
|
| |
this allows for creating custom URI "schemas" in the linter's config,
which may be either allowed, prefixed, or translated according to
some (domain-based) substitution.
|
|
|
|
|
|
| |
(these use a rather crude regex for parsing, which may be possible to
side-step, and which should probably be replaced by something that was
actually written while following the relevant rfc)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
also yet another typeclass™, because why not?
|
| |
|
|
This got kinda out of hand, but it can now (a) read a json config file
and (b) patch that with another json given on the command line to change
some of the options given in the file.
No, I probably didn't need to make the `patch` function sufficiently
general to work with arbitrary records, but it was kinda fun to do.
|