When migrating to the latest version 13.1.0, I noticed the changes in the assignment of ActivityCodeValue to ActivityCode. In older library versions the method addValue(Integer uniqueID, Integer sequenceNumber, String name, String description, Color color) was deprecated and it is now completely removed. Documentation for the deprecation was as follows @deprecated use ActivityCodeValue.Builder and pass result to addValue(ActivityCodeValue) method but in the end there is no method addValue(ActivityCodeValue) and one has to use activityCode.getValues().add(activityCodeValue) to add new ActivityCodeValue to ensure it will be included in the exported file.
This is more like a suggestion to add new method addValue(ActivityCodeValue) as initially intended based on the deprecation comment to have a cleaner way for adding new ActivityCodeValues since one has to first verify that activityCode.getValues() is returning mutable collection.
When migrating to the latest version 13.1.0, I noticed the changes in the assignment of
ActivityCodeValue
toActivityCode
. In older library versions the methodaddValue(Integer uniqueID, Integer sequenceNumber, String name, String description, Color color)
was deprecated and it is now completely removed. Documentation for the deprecation was as follows@deprecated use ActivityCodeValue.Builder and pass result to addValue(ActivityCodeValue) method
but in the end there is no methodaddValue(ActivityCodeValue)
and one has to useactivityCode.getValues().add(activityCodeValue)
to add newActivityCodeValue
to ensure it will be included in the exported file. This is more like a suggestion to add new methodaddValue(ActivityCodeValue)
as initially intended based on the deprecation comment to have a cleaner way for adding newActivityCodeValue
s since one has to first verify thatactivityCode.getValues()
is returning mutable collection.