These are chat archives for spring-cloud/spring-cloud
ExpanderAPI extracts a
Stringrepresentation of a parameter in order to insert it into the REST request URI.
enumtype as a parameter. Enabling a Spring conversion-based
Param.Expanderallows this to "just work" without having to modify the
SpringMvcContractto handle some form equivalent to Feign's
if (isHttpAnnotation ...)
FeignClientsConfigurationto pass in an instance autowired from the
ApplicationContext. Does that seem appropriate?
ConversionServicesin the context
ConversionServicefor both purposes, and your comment would seem to agree. And I agree with what you said there; just not sure how to implement.
ConversionServiceis going to get the default one, and since you said that would be a start I will go ahead and update the PR in this manner.
FormattingConversionServicewhich is indeed modified using
WebMvcConfigurers, but those actually use the
FormatterRegistryinterface to modify the aforementioned
FCS.I suppose it would be possible to mimic this format but it's not clear to me how to properly inject the default
ConversionServicefor use as a default, I suppose in the absence of any
FormattingConversionServiceas does Spring MVC and have done with it.