Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-35875

Cook up a documentation scheme for BO extensionpoints

      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

          Josh McDonald added a comment -

          Probably needs prioritising – or WONTFIXing and whatever other Jira metadata is needed.

          Josh McDonald added a comment - Probably needs prioritising – or WONTFIXing and whatever other Jira metadata is needed.

          James Dumay added a comment -

          Probably deserves its own epic

          James Dumay added a comment - Probably deserves its own epic

            Unassigned Unassigned
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: