Does amper not support plugins yet? Only some bles...

# amper

[Lee Hayeon]

Does amper not support plugins yet? Only some blessed ones like Spring, Ktor, Lombok, etc?

[Anton Prokhorov]

Hi, only blessed one so far
Extensibility is our one of the main focus though, we are working on it

[Lee Hayeon]

Great, no problem. I was just asking because the current configuration didn’t seem scalable, and I couldn’t find how to use custom plugins

[Anton Prokhorov]

didn’t seem scalable

what kind of scalability are you looking for?
could you please elaborate a bit more?

or maybe you have some plugins you need in mind
or maybe some inhouse stuff you do and would like to write plugin yourself for

Feel free to share anything that pops up on top of your head

[Lee Hayeon]

Something like settings.springBoot, springBoot being literally an option name seemed off. I thought Amper is not supposed to bake in specific frameworks like that. Usually tools go through plugins and treat frameworks and libraries equally. Or does Amper intentionally give very popular framework/libraries special treatment?

[Lee Hayeon]

Like someone may ask why my <random library name> cannot be configured automatically with settings.<random library name> ?

[Lee Hayeon]

Well I’m not actually against treating those giant framework/libraries specially, just saying

[Anton Prokhorov]

> Or does Amper intentionally give very popular framework/libraries special treatment?
Yes, and it is supposed to be a plugin, however, since we have no extensibility yet, you can perceive it as an built-in plugin

> Like someone may ask why my random library name cannot be configured automatically with settings.<random library name> ?
It depends on the mechanism how exactly we implement "enabling" plugins and what exactly "enabling" is

For example, we may be considering an option to configure plugins by settings.<arbitrary plugin id> , it may be just a coincidence that the plugin id matches the library name

I can't be more specific because design extensibility discussions and refinements are happening right now, and the design might have been changed by the implementation

Summing up, we are working on extensibility now, I am compelled to ask to wait a bit more

I hope I answered your question

But I was more curious about whether you have some specific scenarios already, what would you use the extensibility for

What is the first extension you would be implementing?

[Lee Hayeon]

I’m not planning to implement any plugins. I was more curious about how the configuration works while learning Amper. I’m totally fine with the built-in extensions Amper provides for now - I don't have any scenarios or anything like that 🙂

[Lee Hayeon]

And yes, you answered my question! Thank you

[Anton Prokhorov]

Cool, feel free to follow up with additional questions and suggestions, and also, if you feel that you need something which has no built-in support, please don't hesitate to share

[arve]

Some candidates / use cases i hope to be able to use via plugins down the line:
• jib
• detekt
• kotlinx-rpc
• ( sqldelight )
I’m also having some problems getting kotest to cooperate with Amper, although this might not be a plugin issue, it might be a me issue

[rmarquis]

A few more, just to add to the list: ktlint, Jetpack Compose Rules (usually used through one of the ktlint gradle plugin, or detekt plugin)