You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a front-end developer, I need to implement the chip component as designed in the design system. This involves changing the icon and positioning it to the left, ensuring compatibility with future versions of PrimeNG, and maintaining all existing functionalities, especially the delete feature.
Acceptance Criteria
Implement the chip component according to the design system specifications.
Change the icon and position it to the left of the chip.
Ensure all existing functionalities of the chip, including the delete feature, are maintained.
Consider creating a directive to manipulate the PrimeNG tag component if necessary.
Verify that the implementation is not deprecated in future PrimeNG versions (specifically PrimeNG 17).
Ensure the implementation is visually consistent with the design system.
Write unit tests to cover the new chip functionality.
Ensure the implementation does not introduce any new bugs or regressions.
Assuming the current implementation of the tag component can be modified to align with the design system. Access to the current codebase, design system documentation, and PrimeNG documentation is required.
Quality Assurance Notes & Workarounds
Quality assurance should verify that the new tag component is visually consistent with the design system and that all functionalities, especially the delete feature, are preserved. Ensure compatibility with future PrimeNG versions and handle any edge cases.
The text was updated successfully, but these errors were encountered:
Parent Issue
#28493
User Story
As a front-end developer, I need to implement the chip component as designed in the design system. This involves changing the icon and positioning it to the left, ensuring compatibility with future versions of PrimeNG, and maintaining all existing functionalities, especially the delete feature.
Acceptance Criteria
Proposed Objective
User Experience Enhancement, Code Maintenance
Proposed Priority
Priority 2 - Important
dotCMS Version
master
External Links
Assumptions & Initiation Needs
Assuming the current implementation of the tag component can be modified to align with the design system. Access to the current codebase, design system documentation, and PrimeNG documentation is required.
Quality Assurance Notes & Workarounds
Quality assurance should verify that the new tag component is visually consistent with the design system and that all functionalities, especially the delete feature, are preserved. Ensure compatibility with future PrimeNG versions and handle any edge cases.
The text was updated successfully, but these errors were encountered: