summaryrefslogtreecommitdiff
path: root/lib (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* moving code aroundstuebinm2021-09-201-57/+69
|
* lint embedded tilesetsstuebinm2021-09-204-11/+21
|
* lint map things that aren't custom propertiesstuebinm2021-09-202-12/+36
|
* lint general map propertiesstuebinm2021-09-204-72/+121
|
* some properties require non-empty layersstuebinm2021-09-194-46/+92
|
* support for properties that aren't stringsstuebinm2021-09-194-49/+88
| | | | apparently i couldn't read or something?
* collecting map dependenciesstuebinm2021-09-184-20/+70
|
* moved types into Types.hsstuebinm2021-09-184-51/+66
| | | | it's almost as if there's some structure to this code!
* can collect dependencies!stuebinm2021-09-184-25/+56
| | | | | | | There's now a Lint type, which may be either a "true lint" (which is a Hint, which contains some message and level of severity), or a Depends, which indicates that this map depends on some ressource or other (and is otherwise treated as a special info Hint in all other cases)
* type check propertiesstuebinm2021-09-183-56/+42
| | | | | | /finally/ figured out that all properties just look like {name, value, type} so now that's abstracted away and Properties.hs doesn't look like javascript anymore
* tame the stringsstuebinm2021-09-184-43/+55
| | | | | | Adds a PrettyPrint typeclass which operates on Text and should replace Show, since constantly converting strings from linked lists to arrays seems somewhat silly.
* (somewhat) reasonable representation of parse errorsstuebinm2021-09-172-17/+41
| | | | | | | | This makes map loading (and parsing) part of the linter, and also makes it return "general lints" and nothing else in case that failed. Possibly a sum type would be nicer here, but I guess it's not really important since everything ends up as json anyways?
* input options, output jsonstuebinm2021-09-163-13/+103
| | | | | | | input options are mostly dummies for now, but some work (e.g. --inpath and --json). Lints can now be optionally printed as json to be reasonably machine-readable (and the json can be pretty-printed to make it human-readable again …).
* some unused codestuebinm2021-09-161-5/+2
|
* moving lots of code aroundstuebinm2021-09-165-0/+607
(also renaming things now that concepts seem a bit clearer)