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

[FEATURE] 🗺️ User Dashboard & Products Pages > Dashboard > implement a reusable segmented control component #149

Open
5 tasks
luqmonac56 opened this issue Jul 19, 2024 · 0 comments

Comments

@luqmonac56
Copy link

figma links:

Description

Develop a reusable Segmented Control component. This component will be used to switch between different views or content sections within the application. The Segmented Control should be visually appealing, responsive, and easy to use. It should include the following features:

Acceptance Criteria

The Segmented Control component is implemented according to the design.
The component should allow customization of segments (labels and values).
Ensure the component is fully responsive and works well across different screen sizes.
The component should handle user interactions such as clicking or tapping on segments.
Ensure accessibility standards are met, including appropriate ARIA roles and keyboard navigation support.

Requirements
The component should receive the following props:

segments: An array of segment objects, each containing label and value.
selected: The value of the currently selected segment.
onChange: A callback function that is triggered when a segment is selected.

Testing

Ensure the component renders correctly with various segment configurations.
Check that the component handles user interactions and updates the selected segment appropriately.
Test the component for responsiveness and accessibility.
Verify that the onChange callback is triggered with the correct value.

Tasks

  • Develop the Segmented Control component based on the provided requirements.
  • Implement handling for segment selection and user interactions.
  • Ensure proper keyboard navigation and ARIA roles for accessibility.
  • Write unit tests to ensure the component works as expected.
  • Test the component for responsiveness and compatibility across different devices.

Top Dashboard Section

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant