Uploaded image for project: 'RH Developer Hub Planning'
  1. RH Developer Hub Planning
  2. RHDHPLAN-463

Prepare a replacement for scalprum-based plugin-targeted APIs

Create Doc EPIC from R...Prepare for Z ReleasePrepare Test Plan (Y R...XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • RHDHPLAN-192Base RHDH frontend on the upstream new frontend system
    • 0% To Do, 100% In Progress, 0% Done
    • M

      Feature Overview (aka. Goal Summary)

      Currently the RHDH frontend application provides, through a scalprum-based untyped API, a way for plugins to read the resolved component wiring configuration.

      Currently this Scalprum API is being used in the RHDH frontend application itself, and by a number of plugins especially in the rhdh-plugins repository.

      That maintains an unwanted dependency to the Scalprum library in plugin source code.
      We have to drop it and replace it by some scalprum-free standard.

      Goals (aka. expected user outcomes)

      The goal is to prepare for the time we will switch the RHDH application to a scalprum-free, pure-module-federation structure.

      Requirements (aka. Acceptance Criteria):

      • It should be possible for plugins to have access to the same wiring configuration without involving any scalprum API at any stage.

      Documentation Considerations

      We would need to provide documentation, at least minimal through some example plugin using the new API.

              stlewis_2 Stan Lewis
              stlewis_2 Stan Lewis
              RHDH Plugins
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: