Hello :wave: Whats the proper way to define required properties/configuration for a custom plugin? d...

# ktor

[Dariusz Kuc]

Hello 👋
Whats the proper way to define required properties/configuration for a custom plugin? docs here show optional values with fallback to default -> https://ktor.io/docs/custom-plugins.html#configuration-file

should I mark those as lateinit? or maybe by using Delegates.notNull()? or is there some more elegant way to do it?

[spand]

I am not sure if the config has a handle for reporting these cases but otherwise it seems defining the fallback as ?: error("config is mandatory but was missing") would be better than whatever funky errors lateinit or notNull produces

[Dariusz Kuc]

yeah its just I wish there was a way to communicate to user if you install this plugin you need to configure those properties (failure at build time - compiler would complain) vs failing at runtime with the info

[Aleksei Tirman [JB]]

Unfortunately, this isn’t possible because a plugin instantiates its configuration object and a user who configures the plugin can only mutate configuration object.