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 Request: Add Arrow Icon for Collapsing and Uncollapsing Split Pane #29

Open
HarshitSahu8 opened this issue Aug 3, 2023 · 0 comments

Comments

@HarshitSahu8
Copy link

Description:
I would like to propose a feature enhancement for the devbookhq/splitter library to add an arrow icon that can indicate and trigger the collapsible state of the split panes.

Use Case:
Currently, when using the devbookhq/splitter library, there is no built-in visual indicator for showing whether a split pane is collapsed or expanded. Adding an arrow icon that points left when a pane is collapsed and right when it's expanded would greatly improve the user experience and make it more intuitive for users to interact with collapsible split panes.

like this:
image

Expected Behavior:
When a split pane is collapsed, the arrow icon should point left (◄), indicating that clicking on the icon will expand the pane. When the pane is expanded, the arrow icon should point right (►), indicating that clicking on the icon will collapse the pane.

Additional Information:

  • I believe this feature would enhance the usability and user experience of the devbookhq/splitter library by providing a clear visual indication of the collapsible state of split panes.

  • This feature aligns well with the common UX patterns seen in other UI libraries and applications.

  • The proposed solution is backwards compatible, as it introduces a new prop that can be optionally used.

Thank you for considering this feature request. I believe that adding the arrow icon functionality will make the devbookhq/splitter library even more user-friendly and valuable for developers. If there are any questions or concerns about the implementation, I'm happy to discuss further.

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