-
Task
-
Resolution: Won't Fix
-
Major
We need to come up with some standard for documenting the built-in extension points in Blue Ocean. While initially most will probably be <ExtensionPoint> components in the the react tree, some (like for example routing) may be either plain functions, or objects. Ideally we would want to be able to find and extract documentation for these, as well as ideally providing a warning if an undocumented (or misspelled) extensionpoint is mapped in a plugin's jenkins-js-extension.yaml file.
[JENKINS-35875] Cook up a documentation scheme for BO extensionpoints
| Assignee | New: James Dumay [ jdumay ] |
| Epic Link | New: UX-137 [ 25631 ] |
| Workflow | Original: CloudBees Default Workflow [ 42260 ] | New: Product Backlog April 2016 v2 [ 43495 ] |
| Status | Original: New [ 10200 ] | New: To Do [ 10003 ] |
| Rank | New: Ranked higher |
| Rank | New: Ranked lower |
V R
made changes -
| Project Import | New: Tue Jun 14 12:50:41 JST 2016 [ 1465876241198 ] |
| Project Import | New: Wed Jun 15 02:53:18 UTC 2016 [ 1465959198925 ] |
| Labels | New: blueocean-imported |
| Component/s | New: blueocean-plugin [ 21481 ] | |
| Key |
Original:
|
New:
|
| Workflow | Original: Product Backlog April 2016 V2 [ 172263 ] | New: JNJira [ 172495 ] |
| Project | Original: User Experience [ 10600 ] | New: Jenkins [ 10172 ] |
| Status | Original: To Do [ 10003 ] | New: Open [ 1 ] |
V R
made changes -
| Assignee | Original: James Dumay [ jdumay ] |