scalameta | Library to read , analyze , transform and generate Scala | Parser library

The only problem here is that you are explicitly casting that KafkaContainer.Def to ContainerDef.

The type of container provided by withContianers, Containter is decided by path dependent type in provided ContainerDef,

That usage is correct.

The docs explicitly say that scalafmt and the sbt plugin are released independently. The plugin version only covers the bits required to integrate scalafmt with sbt: it will download the version of scalafmt specified in .scalafmt.conf as needed. In short, scalafmt and the sbt plugin will almost surely not have the same version number.

You can check on the central Maven repository which versions of the project is available for which version of Scala:

https://mvnrepository.com/artifact/org.scalameta/semanticdb-scalac

The only version built for Scala 2.13.6 is 4.4.18 as of today.

This info is probably also available on their GitHub release note oages

If your test extends munit.ScalaCheckSuite, there is a protected def scalaCheckTestParameters you can override to set the test parameters. A good way to set it is to modify the value in the base class, for example

Document how to run or debug applications #2005 added official debugging documentation at Running and debugging your code which documents two approaches

1. via code lenses run | debug
2. via a launch.json configuration

Here is a hello world example how to debug a test using VSC and Metals via launch.json approach. We will use lihaoyi/utest library and set a breakpoint in a test.

1. Execute sbt new scala/scala-seed.g8 to create correct project structure

2. Open... sbt project with VSC or simply cd into project and execute code .

3. Replace ScalaTest with utest in build.sbt

Switch on "-P:semanticdb:synthetics:on" in build.sbt

Assuming that you're using coc-metals

The README.md of scala-newtype says:

This expands into a type and companion object definition, so newtypes must be defined in an object or package object.

Macros are allowed to expand classes into other classes with the same name and companion objects, but from what I can tell, the newtype annotation turns your case class into an object of the same name (along with a type alias like type DbUrl = DbUrl.Type). This behavior (turning a top-level annottee into a tree of some other kind) isn't allowed. If the annotation had generated a class DbUrl, and maybe an object of the same name, though, it would have been all right, but pretty much anything else won't work.

To fix your problem, all you need to do is move this into a package object (or some other scope, as long as it isn't top-level).

Edit: As Dmytro Mitin pointed out, the created type is not the type of DbUrl but rather something like type DbUrl = DbUrl.Type with an uppercase "T", where the definition of DbUrl.Type looks something like this (I'm just copying this from the README):

Scalafmt seeems to work in VSC with Metals out-of-the-box on my machine

Metals automatically uses Scalafmt to respond to formatting requests from the editor, according to the configuration defined in .scalafmt.conf... if there is no .scalafmt.conf, upon receiving the first format request Metals will create the .scalafmt.conf file for you.

Simply execute Format Document command from Command Palette in VSC and it should format according to .scalafmt.conf. If you would like to continuously format and compile on every source change and scalafmtOnCompile is not working, then try executing in sbt