Open jaredkrinke opened 2 years ago
Even with 20 concurrent requests, checking all external links takes several seconds for my fairly small site (which builds and checks in less than a second without external link checking).
I'd like to avoid caching anything to disk because then there'd need to be policies around invalidating the cache, etc. Results could be cached in memory to speed up rebuilds in the watch/serve scenarios, but I think the only reasonable design is to make this opt-in behavior.
Because this can be slow, it should also have some logging to indicate progress.
Possible design:
This seems handy, but is it worth spending time on a feature that is not used by default?
Added a FAQ entry with an example of using a separate tool for checking external links:
https://jaredkrinke.github.io/md2blog/posts/faq/checking-external-links.html
With that in place, I'm deferring this work to a future release.
As long as it doesn't slow down reloads. Maybe make it optional?