Plans to Support Scala 3 ?

[Javakky-pxv]

Hello, I am @Javakky-pxv , a maintainer for the play-swagger that Open API Doc Generator. We've always appreciated using your repository for generating documentation with scaladoc. Thank you for your work.

With the release of Scala 3.3.0 (LTS) and Play's announced support for it (https://github.com/playframework/playframework/issues/11260), we are considering updating our repository to support Scala 3.

As part of updating our repository, we'd like to use an embedded Scaladoc that supports Scala 3. Do you have any plans to update your repository to support this?

After looking at the scala-library3, it seems challenging to transition as is, so I am considering the following three options:

• Develop a new one that supports Scala 3 myself
• Submit a PR to your repository to make it compatible with Scala 3
• Have you implement support for Scala 3 (if you were originally motivated to do so)

I would appreciate your thoughts on this matter. Thank you.

[henricook]

Given the delay in response here @Javakky-pxv - what are you thinking? I'm someone who'd like to use play-swagger in my scala 3 project

[mjhoy]

@Javakky-pxv curious if you're familiar with scala 3 compiler plugins. I've been looking at how one might rewrite this and it seems slightly non-trivial — so far, I've run into:

• The Tree-extending case classes no longer provide a public copy method, so I'm a little unsure in how to transform them in the same way they are here
• The whole scaladoc infrastructure appears to have been rewritten, and I am not sure (yet) what the equivalent to ScaladocSyntaxAnalyzer is

Plan to keep poking at this but curious if you had any experience/thoughts.

[cruiztorresj]

I asked at Scala's reddit about some projects needing help migrating to Scala 3. I am seeing this issue open. I have some spare time perhaps I can use trying to collaborate here. Do you want to migrate this codebase to Scala 3? What is it that you want to fix? Should I reproduce this issue by creating a Scala 3 project and try to see the documentation at runtime as portrayed in this project's README file?

Thanks