Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-31949

Update Foreman core to PatternFly 5 (remaining work)

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • 6.20.0
    • None
    • None
    • None
    • PF 3 to PF 5 in foreman core (remaining work)
    • In Progress
    • SAT-17164 - Update components to PatternFly 5
    • 3.18
    • False
    • sat-endeavour
    • None
    • None
    • None

      Goal:

      Foreman itself should only use PF5 and remove any use of PF3. Some components should be updated while others should be deprecated and eventually removed.

      In the code you can recognize PF3 imports as something that imports from patternfly-react while PF5 imports from @patternfly/react-*.

      Removing the PF3-based deprecations is out of scope for this epic.

      Acceptance Criteria:

      • No imports from patternfly-react except in deprecated components
      • Any test automation that fails after refactor is updated to reflect the changes
      • Jira issues are created for use of deprecated components in plugins shipped by Satellite

      Open questions:

      • Which components need to updated?
      • Is just grepping for patternfly-react sufficient to make sure we find all the work or are there other libraries we need to get rid of?
      • Are there any wrappers using deprecated components?

      Implementation hints

      Look inĀ https://v5-archive.patternfly.org/ which component has the same name/similar usage and use it instead of the existing one.
      PF5 components might have different structure, props, or usage.
      If the component has snapshot tests please replace them with React Testing Library tests or Capybara tests.

              Unassigned Unassigned
              lvrtelov@redhat.com Lucie Vrtelova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: