| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
(and `url` is, too)
|
| |
|
|
|
|
|
| |
(since we're starting to get maps that actually pass linting, we also
get to find more bugs! yay!)
|
| |
|
|
|
|
| |
(following a discussion with hxchn)
|
| |
|
|
|
|
| |
might be useful to have
|
|
|
|
|
|
|
|
|
|
| |
this just checks for maps from which it's impossible to reach
`main.json`, and then gives a warning. Properly it should check if these
maps have an exit to outside the repository (in which case it may give a
suggestion, and an error otherwise).
Also, redid some of the CheckDir code. No idea what that mess was, but
it's marginally nicer now.
|
|
|
|
| |
(it didn't check if directories to save maps in actually existed)
|
|
|
|
|
| |
these now have their own top-level config attribute which is essentially a
shorthand for setting one that's deeper nested.
|
|
|
|
|
|
|
|
|
| |
So far i've never found an instance of -Wname-shadowing telling me
anything useful, so it's disabled now, and most of the other trivial
ones are fixed.
(I assume this means I'll need -Wname-shadowing in about a day or two to
find some bug ...)
|
| |
|
| |
|
| |
|
|
|
|
| |
(this seems to be a common mistake so far)
|
|
|
|
|
| |
(shouldn't have been called anyways, but it's still nice not to have it
fail if it ever does get called with that case)
|
| |
|
| |
|
|
|
|
|
| |
(before it would fail to find e.g. the start layer if it wasn't a
top-level layer)
|
|
|
|
|
| |
The script inject doesn't do anything for now; guess I'll re-add that
once we actually have a URI for that.
|
|
|
|
|
| |
(these were `error` before, which didn't really make sense, since
workadventure can deal with them, they're just not allowed at rc3)
|
|
|
|
| |
also, float properties exist, apparently
|
|
|
|
| |
(in which case it just doesn't do anything at all)
|
| |
|
| |
|
|
|
|
| |
(the format used last year is no longer applicable to this year's event)
|
|
|
|
| |
(found by running through rc3 2021 map submissions and looking at what failed)
|
|
|
|
|
| |
(as per today's discussion with tabascoeye, mapCopyright should not be
required, though I've left it as recommended)
|
| |
|
|
|
|
|
| |
(previously it would just lint "can't use name twice" multiple times,
which looks kind of silly)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
(forgot that `error` is the builtin haskell function; the one to create
linter errors is called `complain`)
|
| |
|
| |
|
|
|
|
|
|
|
| |
it was kinda getting messy in places.
Also found some accidental isomorphisms between types, so these are now
only one type because the consequences were getting silly.
|
| |
|
|
|
|
|
| |
this includes a halfway-reasonable parsing of object layers, as well as
some monad plumbing to get them all in the right place.
|
|
|
|
|
|
| |
because we can't ever trust workadventure, apparently.
why are we using that thing again?
|
|
|
|
|
| |
(to prevent name clashes between assemblies; shared jitsi rooms are
still possible simply by letting their names start with "shared-")
|
|
|
|
|
| |
(since otherwise we might run into namespace clashes for assemblies with
funny names)
|
|
|
|
|
|
| |
since the scripting API can define new properties and we (for now) do
not know what the script may or may not be able to do, the linter would
otherwise reject potentially valid maps.
|
|
|
|
|
|
| |
("rudimentary" since for now the best it can do is just replacing /
prepending urls; presumably, it should also do a sanity check or
something of the like)
|
|
|
|
|
|
|
|
|
|
| |
Among them
- always set correct exit codes
- refuse to write out files if the out path already exists
- calculate the overall severity correctly
- slightly changed the json output schema
- also output the text output format in json
- make the default config.json suitable for a production environment
|
|
|
|
| |
some parts of haskell are really, really old …
|
| |
|
| |
|
|
|
|
|
|
| |
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)
|