io-silentwhich combines the behaviours, which is not ideal
Hi, we have some strange behaviour during "unidoc", it's unrelated to
mdoc I suppose, but I have no idea where to ask.
We have strange behaviour during our docs construction, seems like during compilation some old version of dependencies, such as cats, and cats-effect are used.
For instance, during doc generation for this file
type mismatch; [error] found : I[cats.effect.concurrent.MVar[F,A]] [error] required: I[cats.effect.concurrent.MVar2[F,A]]
sbt/sbtchannel might be better to ask
docsfolder, but as I see Docusaurus handle only static assets in
website/static. Is there some common way to work with images?
website/staticwhich have to be added to
.gitignore. I just asking if there something better than this, or some built-in code for it.
I was trying to explore mdoc in a sample project following the documentation. I have added the plugin in
plugins.sbt and created two projects in
build.sbt where docuemntation project depends on my root project as given in the documentation. However, when I run
docs/mdoc I get error for dependency resolution as mdoc is looking for
2.12 version of the project but I am using
addSbtPlugin("org.scalameta" %% "sbt-mdoc" % "2.2.21")
lazy val `sample-project` = project .in(file(".")) .settings( name := "sample-project", version := "0.1", scalaVersion := "2.13.3" ) lazy val docs = project // new documentation project .in(file("myproject-docs")) // important: it must not be docs/ .settings( mdocVariables := Map("VERSION" -> version.value, "SCALA_VERSION" -> "2.13.3") ) .dependsOn(`sample-project`) .enablePlugins(MdocPlugin)
What am I missing?
scalaVersionto 2.13.13 on the docs project as well
Hi everyone, i was wondering if anyone is using mdoc with scala3 ... im running into this issue where im trying to use scala3 syntax in mdoc but for some reason it's failing on this:
error: /Users/tomas.herman/workspace/datadog4s/site/docs/userguide.md:180:41: `_` is no longer supported for a wildcard import; use `*` instead This construct can be rewritten automatically under -rewrite -source future-migration. import com.avast.datadog4s.extension.jvm.*
Basically it's complaining about
_ not being supported and forcing me to use
*, which is fine ... but i'm already using
Any ideas why that is?
@tomasherman: the scala 3 support is supper new and you might be the first person to actually test it :) is this issue minimizable or at least somewhere I can take a look at a reproduction?
I'm asking because the code generator for Scala 3 is new and different, so it may as well have problems