Plugin development : Extension validation vs default values

plugins

(Maxim Chouinard) #1

Hi guys,

I am currently developing a plugin that connect to a server instance to execute task and i use the extension as configuration for it.

In some way, the default values look more attractive but in my case, the extension inputs doesn t add a plus value since those are the connection url + creds.

Is it a good practice to validate that the extensions are defined when applying the plugin, otherwise i could probably validate it in the tasks type that need those configurations?

Maybe there is something that i’m missunderstanding.

Thanks


(Benjamin Muschko) #2

If you use custom task annotations for input and output properties then you already have validation built-in. You don’t need to write it yourself. I’d keep the validation to the custom task and would not implement any validation logic in the extension. Usually the extension property values propagate down to the custom task properties in some form anyway.


(Maxim Chouinard) #3

was awfully using the annotation in the extension, thanks