Today there is a `module.yaml` config option `set...

# kotlin-toolchain

[arve]

Today there is a module.yaml config option settings.publishing.name which (I assume) defines the artifact name.

What are the chances of getting a similar setting for internal amper “module name”?
We have a naming and project convention where all services have separate contract and service modules.

e.g.

serviceA/
   contract/
   service/
serviceB/
   contract/    // interface here
   service/     // implementation here
...

If I try to replicate this structure in Amper, it fails with module collision, and I am forced to flatten the folder hierarchy in order for Amper to derive a unique module name for each module. This quickly becomes very hard to navigate in a large project

serviceA.contract/
serviceA.service/
serviceB.contract/
serviceB.service/

Support for defining a convention would be cool, but also probably complex to implement. I wouldn’t mind having to define module name in each module.yaml for example, which I assume would be much easier to implement

[joffrey]

Hi Arve! Thanks for the report. We are aware of this specific issue, and we will do something about it. The constraint about unique module names might be removed, or we might introduce an explicit module name property in module.yaml

[arve]

Great news, thanks @joffrey! Very much looking forward to it 🙌