Regarding new version catalog support, should it b...

# amper

[John O'Reilly]

Regarding new version catalog support, should it be possible right now to use bundles?

[Joffrey]

I don't have the answer right now from the top of my head (I think it's not supported right now). In the meantime, could you please share what you use bundles for? What is your use case?

[John O'Reilly]

Mostly for combining various Ktor dependences

[Joffrey]

Combining dependencies on its own can be done in module.yaml, do you need to share this combination between modules?

[Joffrey]

If yes, wouldn't templates solve your problem?

[John O'Reilly]

Mostly right now about being able to reuse existing toml file as is

[Joffrey]

I see, that makes sense for sure, and is a very valid need

[John O'Reilly]

And makes I think module.yaml file more succinct and readable

[Joffrey]

I was rather asking about why you used bundles in Gradle in the first place to understand the use cases. I have found that, in practice, bundles were heavily misused and led to adding unnecessary dependencies in lots of subprojects (at least from my experience). Usually, it turned out better to directly declare the dependencies each module needed, or to use convention plugins to define types of projects that required the same dependencies by essence, and define their dependencies there.

[Joffrey]

> And makes I think module.yaml file more succinct and readable
Yes, and that can also be achieved with convention plugins in Gradle. In Amper, the equivalent would be to use templates. That's why I'm investigating use cases, and checking whether these would be acceptable solutions in the long term 🙂

[Anton Prokhorov]

I don't have the answer right now from the top of my head

Confirmed, we don't support bundles now