| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
I found yet more properties that weren't really documented or weren't
marked as optional, hurray!
|
| |
|
|
|
|
|
|
| |
the unhelpfulness of the spec is slowly starting to grate …
Anyways, apparently a lot more properties don't have to be present, and
you find out by finding maps somewhere that work but currently fail the
parser.
|
| |
|
|
|
| |
(didn't do anything, and it seems better to do all of these things in
the config anyways)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(this would otherwise break the json schema if `--json` is given)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
since the older versions of Aeson can be attacked via hash-flooding.
|
| | |
|
| | |
|
| |
|
|
| |
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.
|
| |
|
|
| |
(but not (yet?) on missing maps/entrypoints)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
(also fix some hlints)
This removes some code that was apparently dead and I never noticed. I
only noticed now since it wouldn't work with the newer versions of Aeson
anymore.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
this also includes some more monad plumbing, and an option for the
linter to actually write things out again. Some of the previous commit
was reverted a bit since it turned out to be stupid, but overall it was
suprisingly easy once I got around to it, so yay! i guess
Also includes a fairly silly example of how to use it.
|
| |
|
|
|
|
|
| |
I'm not sure if this is the right approach tbh — it lets the LintWriter monad
modify its own context, but maybe we might run into cases where lints and
modifications depend on each other across longer "distances" than just the
context of the linter (i.e. just across a property?)
|
| | |
|
| |
|
|
|
| |
(and one that contains almost only mempty can be written much shorter
than I thought it could)
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(apparently, some of them aren't even in the spec, just the changelog!)
|
| |
|
|
| |
the previous state was a hacky mess
|
| |
|
|
|
|
|
|
| |
for now, just with layers. Instead of listing by layer (and giving
lints multiple times), list by lint type (and list all layers in which
this lint was applicable).
This is a bit wonky for now, but readability of output is much better.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This cleans up all the old rubble that came from the Tiled package I
originally took from hackage. It now uses generics instead of
implementing all the ToJSON and FromJSON instances by hand, and
(deserialize . serialise) will now actually return a (semantically)
equivalent json.
It'll now also reject keys that it doesn't know, which required adding
some in several places which the tiled package didn't know about (or
which were introduced after it was originally written, dunno).
Several more Maybes are required now, to represent the difference
between e.g. empty lists and on set value, which does make the code
slightly weirder in other places …
|
| |
|
|
|
| |
the previous state appears to have been an oversight and made no sense
at all.
|
| |
|
|
|
|
| |
this reorganised the whole linting for tilesets somewhat; it's now very
similar to that linting layers, and it may be possible to abstract some
of the code away ...
|
| | |
|
| |
|
|
|
| |
the build artefacts should be relocatable and run on (almost?) every
system that has a linux kernel underneath.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
