Remove generics from Message/Profile context, handler, action, etc. APIs
Basics
Logistics
Basics
Logistics
Description
Environment
None
Activity
Show:
Scott Cantor July 31, 2019 at 4:53 PM
Committed changes.
One known remaining set of issues is the context navigation function set that rely on unchecked casts of the returned contexts. They should be changed to take a Class parameter for the expected context type and do a programmatic cast and/or a more controlled error check.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Scott Cantor
Scott CantorReporter
Scott Cantor
Scott CantorFix versions
Created July 31, 2019 at 4:40 PM
Updated March 11, 2020 at 2:10 PM
Resolved August 2, 2019 at 1:31 PM
It has proven impossible to get all of the code building when the compiler is set to fail on various sorts of issues with generic types. The extensive nesting of generic types within other generic types is also apparently impossible to pull off.
After remediating the generics out, the impact on the code base itself other than just type declarations was minimal and in many cases actually improved error detection by turning runtime exceptions from class casts into properly declared exceptions.
No tests appear to have broken so far but there may a straggler to fix once it's fully building.