If you are looking for a workaround, you can create your own implementation (which extends CollectionEditorDescriptor<CommerceMediaModel> ), and use this attribute
[EditorDescriptorRegistration(TargetType = typeof(ItemCollection<CommerceMedia>), UIHint = SystemUiHint.CommerceMediaCollection, EditorDescriptorBehavior = PlacedLast )]
Then you can add your types into AllowedTypes
I think that should work, but I haven't tried myself
Thanks Quan Mai, creating a custom implementation for that EditorDescriptor worked, so that solves the Nice to have I initally asked for.
To answer Surjit Bharath question, yes I am reporting a bug:
and also trying to help with debug info so that it makes it easier for Optimizely engineers to fix it.
Drag & drop assets within the Assets tab in Commerce Catalog UI used to work just fine on the .net-framework version of the platform, so I see no reason why it should work in the .net5/6 versions.
Drag & drop assets within the Assets tab on the any of the Commerce Entities (Categories, Products, Variants, etc) does not work.
Debug info:
CommerceMediaCollectionEditorDescriptor uses the LinkableTypes property from MediaRepositoryDescriptor to set the AllowedTypes in the editor descriptor, but the LinkableTypes is never set.
Nice to have besides fixing the bug:
AllowedTypes (from CommerceMediaCollectionEditorDescriptor) should allow not only Optimizely Media Content Types, but also content coming from 3rd party (e.g. DAM connectors)