Can you outline how RL modules would be handled
in the transclusion
scenario?
The current patch does not really address that problem, I'm afraid. I can
think
of two solutions:
* Create an SyntheticHtmlContent class that would hold meta info about
modules
etc, just like ParserOutput - perhaps it would just contain a ParserOutput
object. And an equvalent SyntheticWikitextContent class, perhaps. That
would
allow us to pass such meta-info around as needed.
* Move the entire logic for HTML based transclusion into the wikitext
parser,
where it can just call getParserOutput() on the respective Content object.
We
would then no longer need the generic infrastructure for HTML transclusion.
Maybe that would be a better solution in the end.
Hm... yes, I should make an alternative patch using that approach, so we
can
compare.
Thanks a lot Daniel, I'm happy to help test / try out any solutions you
want to experiment with. I've moved my work to gerrit:
the last commit (with a lot of help from Matt F.) may be ready for you
to use as a use case. Let me know if it'd be helpful to install this
somewhere in labs.