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.
We are using
anytype 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 usesanyas 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 ofKurtwhere the adapter calls are composed together, due to not having strong typing on the interchange types that flow between the composed calls.