Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update components to use new JSX transform #11553

Open
mfrances17 opened this issue Feb 20, 2025 · 0 comments · May be fixed by #11582
Open

Update components to use new JSX transform #11553

mfrances17 opened this issue Feb 20, 2025 · 0 comments · May be fixed by #11582
Assignees
Milestone

Comments

@mfrances17
Copy link
Contributor

Describe the enhancement or change
This is a follow up to #11524 in which the new JSX transform was introduced, which removes the need to import React in every file that contains JSX. Currently the linter is configured to warn on all violations. This issue will require running the react codemods to automatically fix the components that import react, but may require some manual work as well so we comply, such as in the case of named imports instead of importing * from react.

Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?
No

Any other information?
The jsx transform changes were actually introduced in React 17, but will be required to add support for React 19.

@mfrances17 mfrances17 self-assigned this Feb 20, 2025
@github-project-automation github-project-automation bot moved this to Needs triage in PatternFly Issues Feb 20, 2025
@thatblindgeye thatblindgeye moved this from Needs triage to Not started in PatternFly Issues Feb 20, 2025
@mfrances17 mfrances17 added this to the 2025.Q1 milestone Feb 24, 2025
@mfrances17 mfrances17 moved this from Not started to In Progress in PatternFly Issues Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

1 participant