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

Fix Issue #300 Correct Dropdown Behavior in FAQ Component #301

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

benbaruka
Copy link
Contributor

@benbaruka benbaruka commented Jan 31, 2025

#300 Noticed that multiple dropdowns in the FAQ section could be open at the same time, causing a confusing user experience.

Solution:
Implemented a fix in the FaqBar component to restrict the interface to only one expanded dropdown at a time. This ensures a cleaner interface and a more straightforward navigation experience.

- Adjusted the useState declaration in the Faq component to accept both number and null values.
- This change resolves TypeScript errors related to state updates and improves the handling of which FAQ item is open.
- The chevron icon in the FaqBar component now points upwards when the dropdown is open and downwards when it is closed.
- This visual cue helps users understand whether the FAQ section is expanded or collapsed.
Copy link

vercel bot commented Jan 31, 2025

@benbaruka is attempting to deploy a commit to the keep-starknet-strange Team on Vercel.

A member of the Team first needs to authorize it.

- The chevron icon in the FaqBar component now points upwards when the dropdown is open and downwards when it is closed.
- This visual cue helps users understand whether the FAQ section is expanded or collapsed.
@benbaruka benbaruka changed the title Fix Issue #300: Correct Dropdown Behavior in FAQ Component Fix Issue #300 Correct Dropdown Behavior in FAQ Component Jan 31, 2025
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

Successfully merging this pull request may close these issues.

1 participant