Deprecate, than remove in next release. It's internal API but we might want to give users relying on it nevertheless a chance to adapt.
Cheers, Uli On Wed, September 2, 2015 10:15, Jochen Kemnade wrote: > Hi, > > we could remove EnumValueEncoderFactory. There's no need for it anymore, > since TypeCoercedValueEncoderFactory steps in to encode/decode anything > that has no specific value encoder and EnumValueEncoder delegates to > TypeCoercer anyway. > I ran the test suite without the EnumValueEncoderFactory and everything > works fine. > Thoughts? > > Jochen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
