It would provide a lot of flexibility if we could specify a transformer-function which runs on the output of each slide.
E.g. an option called transformSlideXML with the signature (inputSlideXML) => string;
So if specified then makeXMLSlide would run the output through this function before returning.
This would give users the option to implement anything you do not support by piping the XML of each slide through this function.
(In my case I would really like to have control over autoplay & looping of videos. I realize this is too much of an ask as a feature. So a transformer function would let me find/replace to add this myself in an elegant way.)
This would essentially let people write mini plugins to patch new features in if they do not have the confidence/familiarity to submit them as PRs. (E.g. in my case I can identify the XML that would need to be added and where to add it but I don't have the confidence to turn this into a PR).
Issue Category
Desired Behavior
It would provide a lot of flexibility if we could specify a transformer-function which runs on the output of each slide.
E.g. an option called transformSlideXML with the signature (inputSlideXML) => string; So if specified then makeXMLSlide would run the output through this function before returning.
This would give users the option to implement anything you do not support by piping the XML of each slide through this function.
(In my case I would really like to have control over autoplay & looping of videos. I realize this is too much of an ask as a feature. So a transformer function would let me find/replace to add this myself in an elegant way.)
This would essentially let people write mini plugins to patch new features in if they do not have the confidence/familiarity to submit them as PRs. (E.g. in my case I can identify the XML that would need to be added and where to add it but I don't have the confidence to turn this into a PR).