Actions
bug #7250
closedadd null checks to TeamDefaultCacheStrategy
Start date:
Due date:
% Done:
50%
Estimated time:
Severity:
normal
Found in Version:
Description
team members are not being null-checked.
In UIs members can be null at a point in the application life cycle when the cache needs to be generated (e.g.: updating ui element labels). Thses Situations are sometimes determined by the UI framework and thus out of the control of the application developer, so we must handle null values in the cache
Updated by Andreas Kohlbecker about 6 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
Applied in changeset cdmlib|02f58c709c8e2ea7cd2bc2a8e0fd529a80be54c2.
Updated by Andreas Kohlbecker about 6 years ago
Andreas Müller, please review the code changes are correct. I was a bit unclear about the role of paramter i
in concatString(Team team, List<Person> teamMembers, int i)
Updated by Andreas Müller about 6 years ago
- Status changed from Resolved to Closed
- Assignee changed from Andreas Müller to Andreas Kohlbecker
looks ok
Actions