| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
i kept being confused by things happening that really shouldn't 🙈
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
this removes:
- the bbb properties
- all explicit mentions of rc3
- the weird script domain hacks (done via a substitution now)
- some (few) of the weirder code choices
it also adds some more type level witchery to deal with configs, which
for some reason seems to be the hardest problem of this entire program …
also the server now does inter-assembly dependency checking!
|
| | |
|
| |
|
|
|
| |
(please only deploy once
https://git.cccv.de/hub/hub/-/merge_requests/492 is also deployed)
|
| | |
|
| | |
|
| |
|
|
|
| |
(audio links now have their own allowlist, which won't put things
through the dereferrer)
|
| |
|
|
|
| |
(this is a temporary solution, since it would invoke the dereferrer for
things that aren't allowed, which is silly)
|
| | |
|
| | |
|
| |
|
|
|
| |
(unfortunately this one's hardcoded, the config options just aren't
general enough)
|
| | |
|
| |
|
|
|
| |
these now have their own top-level config attribute which is essentially a
shorthand for setting one that's deeper nested.
|
| |
|
|
|
|
| |
("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
|
| |
|
|
|
|
| |
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)
|
| | |
|
| | |
|
| | |
|
| |
|
