patternfly / patternfly/chatbot
Look at switching/providing alternative to ChatBotHeaderSelectorDropdown
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6
- Forks
- 37
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 5
Description
From @thatblindgeye: @rebeccaalpert ideally I think we should be using a Select component for this ChatbotHeaderOptionsDropdown, same for the ChatbotHeaderSelectorDropdown, assuming the intent will always be "selecting" something in these 2 chatbot components. Dropdown should really be used to initiate an action/navigate to a link, whereas a Select for "selecting" things which seems more applicable in this case.
Not a blocker for this PR, and maybe it's something we need to wait for a breaking change for, but probably worth opening an issue for this. Maybe chatbot has both a "ChatbotHeaderSelector" and "ChatbotHeaderDropdown" to achieve whatever goals a consumer may need?
Jira Issue: PF-2377
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
Start by reviewing Jira issue PF-2377 and locating ChatbotHeaderOptionsDropdown and ChatbotHeaderSelectorDropdown. Determine whether these components should use Select or whether separate selector and dropdown components are needed; done requires a settled consumer-facing direction and agreement on any breaking-change implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100