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

[1:1] pfe-code-block #2093

Closed
bennypowers opened this issue Aug 11, 2022 · 0 comments · Fixed by #2233
Closed

[1:1] pfe-code-block #2093

bennypowers opened this issue Aug 11, 2022 · 0 comments · Fixed by #2233
Assignees
Labels
1:1 Aligning components with PatternFly v4 priority: high Severity level: 1

Comments

@bennypowers
Copy link
Member

Component name: <pfe-code-block>

The code-block component exists in PFv4 and PFE. It will be updated in PFE and migrated to RHDS.

Design specification

PatternFly v4 Code Block

@bennypowers bennypowers added this to the PatternFly 1:1 milestone Aug 11, 2022
@bennypowers bennypowers added 1:1 Aligning components with PatternFly v4 priority: medium Severity level: 2 design system Updates or issues to align components to the Red Hat Design System. update component request needs: prioritization To be prioritized for dev labels Aug 11, 2022
@bennypowers bennypowers removed priority: medium Severity level: 2 design system Updates or issues to align components to the Red Hat Design System. update component request needs: prioritization To be prioritized for dev labels Aug 11, 2022
@kylebuch8 kylebuch8 self-assigned this Oct 11, 2022
@markcaron markcaron added the priority: high Severity level: 1 label Oct 20, 2022
@paigenotfound404 paigenotfound404 moved this from Backlog to In Progress in Red Hat Design System Nov 22, 2022
Repository owner moved this from In Progress to Done in Red Hat Design System Dec 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1:1 Aligning components with PatternFly v4 priority: high Severity level: 1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants