I'm not sure if this is strictly related to scald atoms or not, but on the project that I am working on, there's this attribute called "data-scald-options" that can contain additional css classes. These are not migrated whithin the TransformDndAtomsToMedias. This also depends on media, because an extra step needs to be done in the text format to allow the class attribute on tag.
The proposed solution is to migrate them as well. I am providing a very basic patch for this to get other opinions, but I am pretty sure that maybe a configuration should be set and default to false to not migrate them unless told to. And also maybe the target attribute should be customizable. For now, I'll provide a basic solution.
Needs work
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Thanks for contributing, we appreciate.
I think a configuration option (default: false) would be nice, indeed: this is not always relevant to migrate classes
Hey, you mean to add an option that by default would not migrate the classes unless enabled?
> an option that by default would not migrate the classes unless enabled?
Yes!
thank you