Skip to content

Fixes #39357 - deprecate LineChart component that uses PF3 LineChart#11001

Open
andreilakatos wants to merge 1 commit into
theforeman:developfrom
andreilakatos:linechart-deprecation
Open

Fixes #39357 - deprecate LineChart component that uses PF3 LineChart#11001
andreilakatos wants to merge 1 commit into
theforeman:developfrom
andreilakatos:linechart-deprecation

Conversation

@andreilakatos
Copy link
Copy Markdown
Contributor

Summary

Add a developer-facing deprecation warning for the PF3 patternfly-react LineChart wrapper (common/charts/LineChart). The warning is emitted once per mount (same pattern as common/table/components/Table), points consumers toward @patternfly/react-charts, and states planned removal in Foreman 3.21.

No user-visible UI changes; behaviour of the chart is unchanged.

How to test

Prerequisites

  • Running Foreman (or webpack dev server) with the React app loading a screen that mounts the registered LineChart component (plugin or core mount point that uses foreman-react/componentRegistry name LineChart).
  • Browser devtools console open (NODE_ENV not production so the warning appears).

Scenarios

  1. Navigate to a page that renders LineChart (if unsure, search mounts / mount_react_component / plugin usage for the LineChart component name).
  2. Confirm a single deprecation warning per chart mount, similar in shape to other PF migrations, e.g.
    DEPRECATION WARNING: you are using deprecated common/charts/LineChart ... will be removed in Foreman 3.21
  3. Confirm the chart still renders and interacts as before (data present / empty states).
  4. (Optional) Run npm test with the LineChart test path to ensure snapshots still pass.

Comment thread webpack/assets/javascripts/react_app/components/common/charts/LineChart/index.js Outdated
Comment thread webpack/assets/javascripts/react_app/components/common/charts/LineChart/index.js Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants