I wonder if perhaps a better approach here would be to include an optional asset property on OCKAnyTask. Then no type casting would be required and we'd still get the desired behavior.

I wonder if perhaps a better approach here would be to include an optional asset property on OCKAnyTask. Then no type casting would be required and we'd still get the desired behavior.

I was going to do this, but I didn't see asset in OCKAnyTask, let me look again...

It looks like asset isn't part of OCKAnyTask from what I can tell (I think this may have happened when OCKObjectCompatible was removed). Do you want me to move it there to see if it will break anything? It seems like it shouldn't.

Looking further back, it looks like the only OCKAny to have asset was OCKAnyContact and the other entities gained it through conforming to the OCKObjectCompatable protocol

The last commit assumes UImage(named: "") will always will return nil which I don't know if that's true

Let me know if you want me to remove the AppIcon asset from being used for this in the sample app. I wanted to provide an example without adding additional assets.

Great work Corey! LGTM!

I like that this will add an example of how to use SFSymbols to the sample app!

I like that this will add an example of how to use SFSymbols to the sample app!

I was hoping to find some SF symbols to match some of the other tasks, but didn't see any other good matches.

Thanks for the PR Corey! 🎉