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

Implement PrimeNg Treeselect in Storybook, implement the design system #28638

Closed
Tracked by #28494
nicobytes opened this issue May 23, 2024 · 0 comments · Fixed by #28666
Closed
Tracked by #28494

Implement PrimeNg Treeselect in Storybook, implement the design system #28638

nicobytes opened this issue May 23, 2024 · 0 comments · Fixed by #28666

Comments

@nicobytes
Copy link
Contributor

nicobytes commented May 23, 2024

Parent Issue

#28494

PR => #28666

User Story

As a UI/UX developer, I want to implement the PrimeNg TreeSelect component within our Storybook environment, adhering to our designated design system, to ensure that it integrates seamlessly with our application's visual and functional standards.

Acceptance Criteria

  • The PrimeNg TreeSelect component is fully implemented in the Storybook with all necessary configurations and customizations.
  • The component must match the styles and behaviors defined in our design system, including colors, fonts, interactions, and accessibility features.

Proposed Objective

Component Integration, Design Standardization

Proposed Priority

Priority 2 - Important

dotCMS Version

master

External Links

Assumptions & Initiation Needs

Quality Assurance Notes & Workarounds

@nicobytes nicobytes self-assigned this May 23, 2024
@nicobytes nicobytes moved this from New to In Progress in dotCMS - Product Planning May 23, 2024
@nicobytes nicobytes linked a pull request May 28, 2024 that will close this issue
@nicobytes nicobytes moved this from In Progress to In Review in dotCMS - Product Planning May 28, 2024
nicobytes added a commit that referenced this issue May 28, 2024
@nicobytes nicobytes moved this from In Review to Internal QA in dotCMS - Product Planning May 29, 2024
@nicobytes nicobytes moved this from Internal QA to Done in dotCMS - Product Planning May 29, 2024
@dsilvam dsilvam removed the Triage label May 29, 2024
@github-project-automation github-project-automation bot moved this from Done to Internal QA in dotCMS - Product Planning May 29, 2024
@nicobytes nicobytes moved this from Internal QA to Done in dotCMS - Product Planning May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants