Matthias Endler

Superseded by https://github.com/lycheeverse/lychee/pull/1489.

Yup, good idea. We could change that. 👍

If you find the time, feel free to create a PR for that. Happy to get it merged.

@thomas-zahner fixed it in `master`. @guettli, in case you want to try, please check out lychee from the sources or wait until the next release.

This is now part of the latest release, 0.16.1.

Here's a minimal example that we can use as a test: ```html div { background-image: url("./lychee.png"); } ``` The problem here (and in your example) is the relative path, `./lychee.png`....

This is more of a feature request than a bug, so I changed the issue title and added the `enhancement` label.

I like it. Does it mean that the status is not the definitive "final" status based on what are the accepted status codes, though? I don't have an opinion on...

You mean using `context` a bit like in Go as a request-scoped key-value store across API boundaries? That would be neat, yeah. The plugin authors could pass arbitrary values down...

My thinking was that if we add `context`, we might as well just make it a key-value store. If `accepted` is the only thing we need for now, that's fine,...