Ólafur Páll Geirsson

Thank you for the detailed report! One workaround for now is to use Docusaurus v1. I'm happy to merge any PR that adds a custom code path to generate Docusaurus...

Opened #129 to at least allow users to disable link hygiene, as a workaround for false positives.

I am concerned about expanding the scope of link hygiene to support more custom setups. I think it might be best to limit the scope to reproducing github.com markdown previews....

That would mean only checking markdown files and report warnings for local links that resolve correctly on github.com (even if they're false positive due to custom site generators, scaladoc, etc.)

One false positive from a docusaurus website ``` warning: editors/tree-view-protocol.md:55:1: Unknown link 'editors/tree-view-protocol.md#metals-treeviewchildren', did you mean 'editors/tree-view-protocol.md#metalstreeviewchildren'? [`metals/treeViewChildren`](#metals-treeviewchildren) request. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ```

@keynmol you are on the right track! The bug lies in the renderer. Would love to see this get fixed. > any usecases in particular you'd want covered in the...

I was afraid this wouldn't be so trivial. The `validate` workaround gets a lot tricker once you have 30 keys of which some are nested, contain arrays and so forth....

Here's roughly what I had in mind: ``` scala case class Foo(col: Option[Int]) val d: Decoder[(ACursor, Foo)] = new Decoder[(ACursor, Foo)] { override def apply(c: HCursor): Result[(ACursor, Foo)] = {...

@travisbrown Wow. That looks amazing. Took me a while to wrap my head around how the state monad works in this example. I'll need to experiment a bit with this...

@travisbrown I think I'll begin with the manual approach and keep my eyes open for parts we could abstract over. Will keep you posted. Thanks a lot for your help!