patternfly / patternfly/patternfly-org
Tabs - use React components instead of HTML classes
Open
Nobody has claimed this yet.
PF Team
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 147
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 2
Description
Similar to https://github.com/patternfly/patternfly-org/issues/4588, we should try to use the Tabs React components rather than the HTML class approach.
Jira Issue: PF-2698
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the Tabs usage in patternfly-org and the related issue #4588, then identify the pages or components still using the HTML class approach. Replace those usages with Tabs React components, using Jira issue PF-2698 for context. Done means the affected tabs use the React components rather than HTML classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100