Fully qualified class names can be used in several other places in the code too, but this is the method that appears to determine if an Element is supported or not, so fixing this should probably help avoid any other custom element conflicts on Element Save behavior.
This PR is for the Craft 3.x branch but I expect this change may be welcome on v4 as well if the same code exists there.
This resolves https://github.com/brilliancenw/craft-algolia-sync/issues/29
Fully qualified class names can be used in several other places in the code too, but this is the method that appears to determine if an Element is supported or not, so fixing this should probably help avoid any other custom element conflicts on Element Save behavior.
This PR is for the Craft 3.x branch but I expect this change may be welcome on v4 as well if the same code exists there.