Page MenuHomePhabricator

THICC: Thread handling
Closed, InvalidPublic

Description

Apparently we can't use multiple of the same role of slot per page, so we can't just have each thread be a slot we add to the page. What this means is we need to either use a single slot that contains all the threads or get that changed in core.

In our case this is probably fine for the time being, as we'll only ever be plonking the threads at the end of a thing for the base use case, and it should simplify the display handling as well?

Event Timeline

So, uh, add new content model for managing threads, I guess?

And each thread is just a separate page. Somewhere. Where?

So it just dumps out the header, then dumps the content of the thiccness pages on the page.

Example content:

{
	"metadata": [],
	"introduction": "This is a header for a single-slot thiccness page or to preface the slot itself! I don't even know!!",
	"thiccness": [
		{
			"thread": "Thread test 2"
		},
		{
			"thread": "Thread test"
		},
		{
			"thread": "Another thread page"
		}
	]
}

Change 511129 had a related patch set uploaded (by Ostrzyciel; owner: Ostrzyciel):
[mediawiki/extensions/THICC@master] bug: T223695

https://gerrit.wikimedia.org/r/511129

Change 511129 had a related patch set uploaded (by Isarra; owner: Ostrzyciel):
[mediawiki/extensions/THICC@master] Do ThiccModelAggregateContent logic

https://gerrit.wikimedia.org/r/511129

Change 511129 merged by Isarra:
[mediawiki/extensions/THICC@master] Do ThiccModelAggregateContent logic

https://gerrit.wikimedia.org/r/511129