Symbols not created for Json case classes in example about metabrowse HOT 5 CLOSED

I just checked which files are used to build the site and it seems the test sources are not there

metadoc.cli.MetadocCli.getSymbols:73 db.documents.map(_.input.syntax): List(
  "paiges/core/src/main/scala/org/typelevel/paiges/Chunk.scala",
  "paiges/core/src/main/scala/org/typelevel/paiges/Doc.scala",
  "paiges/core/src/main/scala/org/typelevel/paiges/Document.scala",
  "paiges/core/src/main/scala/org/typelevel/paiges/package.scala",
  "paiges/core/src/test/scala/org/typelevel/paiges/DocumentTests.scala",
  "paiges/core/src/test/scala/org/typelevel/paiges/Generators.scala",
  "paiges/core/src/test/scala/org/typelevel/paiges/JsonTest.scala",
  "paiges/core/src/test/scala/org/typelevel/paiges/PaigesTest.scala"
)

I'm gonna refactor the cli to

• improve testing #60
• improve performance #52
  I can try to fix this along the way.

from metabrowse.

Great. I hope we can also figure out a way to use the sbt plugin code to replace or implement the metadoc-site command.

from metabrowse.

It seems the symbol is resolved but to a 404, I suspect that the resolved symbol is the case class apply which is not present in the source file. Should be fixable.

from metabrowse.

No wait, it seems the problem is cause by the fact that JArray(...) references the synthetic companion object/term and case class JArray references the JArray type. This are two different symbols, we can fallback to a "normalized" match if the exact match doesn't work like I sometimes do in scalafix, that should solve it.

from metabrowse.

Fixed in #75

from metabrowse.