themesberg / themesberg/flowbite
Flowbite Navigation Routing Mistake
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 862
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When on the Flowbite Blocks site, after clicking on a block, the bread crumbs appears. Clicking on the category takes you to /blocks/[category]. This page is correct, however it also shows a drop down selector that (should) let you change the block category, however it does not Route the user to a different page, however it filters the showing blocks.
To Reproduce
Steps to reproduce the behavior:
- Go to 'flowbite.com/blocks'
- Click on any block
- Click on the category in the bread bar (marketing)
- Select a different category. -> results in the error
Expected behavior
When the user is on https://flowbite.com/blocks/ and they select a desired category, the showing blocks properly filter, however when the user navigates back from a block via the bread crumbs, they navigate to https://flowbite.com/blocks/marketing/. This results in only the Marketing blocks to be shown regardless of the category selected in the dropdown.
Desktop (please complete the following information):
- OS: MacOS
- Browser Safari
Additional context
I suspect that the dropdown filters the available blocks, however it can't filter what's not there.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue at /blocks/, then follow a block link to /blocks/marketing/ and use the category dropdown. Inspect the breadcrumb navigation and category selector entry points to determine why filtering remains scoped to marketing; done means selecting another category after breadcrumb navigation shows that category's blocks correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, tailwindcss
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100