I think at a minimum we should add an analog for SpatVectorCollection (i.e. tar_terra_svc() for terra::svc() results)
My initial response in the case of lists, which can be nested and heterogeneous, is that this may be a bit difficult to handle in general for geotargets methods.
However I can totally see the utility of list columns within a data.frame being a useful way to manage multiple terra objects and their metadata... so this is perhaps worth considering more.
Originally posted by @brownag in https://github.com/njtierney/geotargets/issues/77#issuecomment-2129740005