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

Embed the extension point data in the original page load

XMLWordPrintable

    • 1.0-m1

      jQuery was added as a stopgap measure for getting the ExtensionPoint metadata. Easiest thing to do is probably to embed this data in the original page (index.jelly) and so remove the need to make any call. Otherwise we need to find http client replacement for jquery.

          [JENKINS-35848] Embed the extension point data in the original page load

          James Dumay added a comment -

          tfennelly why not use Fetch?

          James Dumay added a comment - tfennelly why not use Fetch ?

          Tom FENNELLY added a comment -

          It won't need either of them once we remove the need to make the call (by embeddeding the data in the original page).

          It could use fetch, but then that's just swapping one dependency for another. Longer term though, it probably would make sense to sort out an externalized fetch package that can be loaded/shared by the browser bundles (vs them all including it).

          Tom FENNELLY added a comment - It won't need either of them once we remove the need to make the call (by embeddeding the data in the original page). It could use fetch, but then that's just swapping one dependency for another. Longer term though, it probably would make sense to sort out an externalized fetch package that can be loaded/shared by the browser bundles (vs them all including it).

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

              Created:
              Updated:
              Resolved: