A modern programming language that makes developers happier.

kotlinlang

Hi folks! we are really eager to hear your thoughts on the new approach to define the project root and the list of modules explicitly by `project.yaml`  file. You can read details in the <https://github.com/JetBrains/amper/blob/release/0.4/docs/Documentation.md#basics|documentation> and the <https://github.com/JetBrains/amper/blob/release/0.4/docs/DSLReference.md#project-file|reference>.
Give it a try and share how it looks and feels. What works smoothly for you? where do you experience friction?, etc
Thanks!

I think explicit wins, and I guess it's faster because there's no need to walk all the subdirectories anymore to find projects. It also makes it easier to disable a module, I like it.

Also, I think the name "project" is much better than Gradle's "settings".

reminds me of pnpms workspace file, I like it

There is an <https://github.com/JetBrains/amper/tree/release/0.4/examples-standalone/compose-multiplatform|example for standalone> but nothing in <https://github.com/JetBrains/amper/tree/release/0.4/examples-gradle|gradle examples>. Does it work the same for gradle? I have tried to convert my amper 0.2 and all gradle tasks disappeared from the IDE. Creating project.yaml did not bring them back…

you need to include your modules in the settings.gradle.kts file <https://youtrack.jetbrains.com/issue/AMPER-393>