Research: Where page.subpages() and wiki.tree() should live

RESOLVED FIXED

Status

RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: openjck, Unassigned)

Tracking

Details

(Whiteboard: p=)

(Reporter)

Description

6 years ago
This is a subtask of bug 810019.

In the meeting today, Luke mentioned that we do not know where the code for page.subpages() and wiki.tree() should live. Each one could be written into the common MDN template or the KumaScript library.
This is the way I've been planning to do it, anyway...

wiki.tree should live here:
    https://developer.mozilla.org/en-US/docs/Template:Dekiscript:Wiki

page.subpages should live here:
    https://developer.mozilla.org/en-US/docs/Template:Dekiscript:Page

wiki.tree should be a kumascript template that uses page.subpages to get the list, and then build the HTML (bug 810027?)

page.subpages should perform an HTTP request to fetch a subtree list (bug 810026?)

And, that subtree list should be implemented in a view on the Django side (bug 810021?)
(Reporter)

Updated

6 years ago
Whiteboard: p=
Going to close this, since I think comment 1 represents the research: 

Both page.subpages and wiki.tree should live in the respective wiki-editable script modules. 

Changes to the kumascript service itself should be very rare, and mainly just for fixing bugs or adding core features to document processing or macro execution. The general trend should be to keep or move wiki-specific things out of core kumascript.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.