Does collections have a defined deprecation policy? I.e. have we made a
promise as to when they are to be deleted, were we to deprecate the
decoration methods in *Utils classes? The way I see it, the wide spread
argument provides a good reason not to delete the methods in a hurry but
Thanks James,
The latter scenario is exactly the one I keep finding myself in! I
guess it's the naming that throws me - the collect() methods provide
what I'd expect of transformedCollection() under a name that seems
pretty abstract, whereas the implementation of transformedCollection()
seem
Really the problem is that the method transformedCollection() got added
to CollectionUtils at all.
Way back at the start of the debates, we had a choice between:
- CollectionUtils.transformedCollection()
- TransformedCollections.collection()
- Transformed.collection()
In the end we settled on
The problem is that the collections you pass in (dates) is supposed to
be decorated. In order to transform the entries on construction there
would need to be some way to alter the values already in dates, but the
Collection interface provides no such direct mechanism.
However, it could be done
Are you wanting to add dates to the resulting collection and have them
transformed into Strings? Or, are you just looking for a collection of
Strings that you don't need to modify which represent the dates? If it's
the latter, you should use the CollectionUtils.collect() method rather than
the
