rubyforgood / rubyforgood/casa
Replace uses of "dropdown" with respective ViewComponent
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 381
- Forks
- 542
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 47
Description
What type(s) of user does this feature affect?

Description
This application uses ViewComponent. While we have made multiple components we haven't replaced old code in all the place where those view components could be used.
Find the places that implement dropdowns but don't use the dropdown component (https://github.com/rubyforgood/casa/blob/main/app/components/dropdown_menu_component.rb). Replace them.
This should be a good place to start with replacements: https://github.com/search?q=repo%3Arubyforgood%2Fcasa+AND+path%3A*.html.erb+AND+%2Fdropdown%5B%22%7C+%5D%2F&type=code
How to access the QA site
Login Details:
Link to QA site
Login Emails:
- volunteer1@example.com view site as a volunteer
- supervisor1@example.com view site as a supervisor
- casa_admin1@example.com view site as an admin
- all_casa_admin1@example.com view site as an all casa admin
- go to
/all_casa_admins/sign_in
- go to
password for all users: 12345678
Questions? Join Slack!
We highly recommend that you join us in slack #casa channel to ask questions quickly. And discord for office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.
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 with app/components/dropdown_menu_component.rb, then review the linked repository search results for dropdown implementations in *.html.erb files. Compare each result with the existing ViewComponent and replace the applicable uses. Done means the identified dropdowns use the respective component without changing their intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100