The demo already has a console that lets you interact with the widgets.
It would be helpful to have a way to see the code that generated the widget and quickly copy it. This helps both in testing and while learning how to use the library.
• Prtksxna | |
May 16 2017, 7:29 AM |
F8164905: image.png | |
May 23 2017, 4:39 AM |
F8098723: Screen-Shot-2017-05-16-at-5.12.19-PM.png | |
May 16 2017, 11:52 AM |
F8098673: Screen Shot 2017-05-16 at 5.12.19 PM.png | |
May 16 2017, 11:52 AM |
The demo already has a console that lets you interact with the widgets.
It would be helpful to have a way to see the code that generated the widget and quickly copy it. This helps both in testing and while learning how to use the library.
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T155473 Improve documentation of OOUI | |||
Resolved | • Prtksxna | T165457 OOjs UI Demos: Show code used to generate widgets | |||
Resolved | Volker_E | T166716 OOjs UI Demos: Make the generated code more discoverable |
Change 353960 had a related patch set uploaded (by Prtksxna; owner: Prtksxna):
[oojs/ui@master] [wip] show code on demo page
Change 353960 merged by jenkins-bot:
[oojs/ui@master] demos: Show code that can be used to create the widget
Thanks. Great improvment.
I see somewidgets did not get the proper code listing. Is this known issue?
No, looks like a bug. That example definitely worked last time I checked that patch. Looks like it was broken by the last patchset.
Change 355205 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
[oojs/ui@master] demos: Fix code generation for more complicated cases
Change 355205 merged by VolkerE:
[oojs/ui@master] demos: Fix code generation for more complicated cases