You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using any type in our codebase in a few places, which need to be cleaned up to use more specific types.
There are some places where this cleanup will be fairly simple, and others less so. The most tricky place for this cleanup is in the KurtAdapter, which currently uses any as a way of being able to ignore the "raw" interchange types of the particular adapter. This usage is problematic because we leave room for certain bugs inside the implementation of Kurt where the adapter calls are composed together, due to not having strong typing on the interchange types that flow between the composed calls.
The text was updated successfully, but these errors were encountered:
We are using
any
type in our codebase in a few places, which need to be cleaned up to use more specific types.There are some places where this cleanup will be fairly simple, and others less so. The most tricky place for this cleanup is in the
KurtAdapter
, which currently usesany
as a way of being able to ignore the "raw" interchange types of the particular adapter. This usage is problematic because we leave room for certain bugs inside the implementation ofKurt
where the adapter calls are composed together, due to not having strong typing on the interchange types that flow between the composed calls.The text was updated successfully, but these errors were encountered: