UI adapters as they are now do a lot. They expose config to the editor, they handle the complexity of exposing the metadata needed for their registration AND their child type handles implementing the logic of the actual adapter. For that reason, and for the reason of needing a adapters composable (can't be monobehaviours) it's important to migrate to the new adapter logic being in non-monobehaviour AdapterImplementation types.
See: https://github.com/HelloKitty/Booma.Proxy/blob/681df58c4ccfb5dd631628c2a0524b5f01e6938a/src/Booma.Proxy.Client.Unity.Common/UI/Abstraction/Implementation/UnityButtonUIButtonAdapterImplementation.cs
UI adapters as they are now do a lot. They expose config to the editor, they handle the complexity of exposing the metadata needed for their registration AND their child type handles implementing the logic of the actual adapter. For that reason, and for the reason of needing a adapters composable (can't be monobehaviours) it's important to migrate to the new adapter logic being in non-monobehaviour AdapterImplementation types.
See: https://github.com/HelloKitty/Booma.Proxy/blob/681df58c4ccfb5dd631628c2a0524b5f01e6938a/src/Booma.Proxy.Client.Unity.Common/UI/Abstraction/Implementation/UnityButtonUIButtonAdapterImplementation.cs