Any reason why a BindingSpec's config should only accept strings?

[sophokles73]

The config property of the BindingSpec object that is used to configure a Target Provider currently is a Map<String, String>. I am currently implementing a generic target provider that serves as kind of a proxy for a standalone target provider. For that, it would be quite helpful to be able to configure the concrete ValidationRule that the generic target provider should use. This would be easy to do, if the BindingSpec's config could contain any JSON type (in particular object) instead of just string. Any reason why this could/should not be changed?

[msftcoderdjw]

1. Evaluate the cost and decide the priority.

[Haishi2016]

Hi @sophokles73, we'll evaluate the impact of change because this is a schema change. If this turns out to be a higher risk, we'll need to push this update to the next API version. At meanwhile, a workaround would be serializing the entire config object into a single property.

[sophokles73]

Thanks for the update. I am currently doing what you are proposing.
The schema that you are referring to, which would need to be changed, is that available somewhere? I would be happy to use that for implementing my uProtocol target provider (also see #635).