Migrate from sbt to bazel

[agluszak]

Closes #613

I also rewrote the Scala codegen in Kotlin, so from now on all generators will use the same IR.

[agluszak]

Cc @KatKlo

[agluszak]

@adpi2 @lefou will you be able to review it this week?

[adpi2]

I can start reviewing it this week, but I have almost no experience with Bazel so I will have more questions than useful comments.

[lefou]

I don't have profound Bazel experience so I can't say anything about the changes. Looks like the docs already mention how to build with bazel. I wonder why all those format changes to the generated source files need to be part of the tooling change. This really obfuscates the more essential change.

[agluszak]

I can start reviewing it this week, but I have almost no experience with Bazel so I will have more questions than useful comments.

No problem, I'll do my best to answer them!

I wonder why all those format changes to the generated source files need to be part of the tooling change. This really obfuscates the more essential change.

That's because bazel-super-formatter I used supports prettier (for the website) and java formatting, but doesn't support scalafmt. I managed to disable java formatting for now, but I'll have to think how to handle scalafmt.

[adpi2]

I managed to disable java formatting for now, but I'll have to think how to handle scalafmt.

You can use coursier to download the scalafmt binary in the repo, and then commit it to the repo:

coursier bootstrap org.scalameta:scalafmt-cli_2.13:3.7.14 \
  -r sonatype:snapshots --main org.scalafmt.cli.Cli \
  --standalone \
  -o scalafmt

[agluszak]

I managed to disable java formatting for now, but I'll have to think how to handle scalafmt.

You can use coursier to download the scalafmt binary in the repo, and then commit it to the repo:

coursier bootstrap org.scalameta:scalafmt-cli_2.13:3.7.14 \
  -r sonatype:snapshots --main org.scalafmt.cli.Cli \
  --standalone \
  -o scalafmt

No need to, I'll plug scalafmt into the existing formatting pipeline, but it's going to take some work. It's already exposed in rules_scala

[agluszak]

@lefou all formatting changes should be gone now

[lefou]

@agluszak Thanks. I have no further comments. LGTM.

[jastice]

From my mostly surface-level review, LGTM! I can't evaluate the deeper logic without serious digging. Questions are only for clarification

[jastice]

will we be able to avoid checking in generated files in the future?

[agluszak]

why?

[lefou]

If they can be automatically generated, they should, unless there are good reasons not to (e.g. the tooling needs some remote resources temporarily unavailable or unstable).