rubyforgood / rubyforgood/casa
Migrate select2 → tom-select
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 381
- Forks
- 542
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 47
Description
Related to https://github.com/rubyforgood/casa/issues/6685
Three call sites (src/select.js, casa_case.js:165, reimbursements.js:77) plus the .select2 class on the report template. tom-select is already a dep and is pattern-proven in controllers/multiple_select_controller.js.
Drop select2 and select2-bootstrap-5-theme and the @use "select2/dist/css/select2" import.
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 src/select.js, casa_case.js:165, reimbursements.js:77, and the report template, then compare their usage with controllers/multiple_select_controller.js. Done means the listed select2 call sites and report-template class use tom-select, the select2 dependencies and CSS import are removed, and the affected frontend behavior remains covered by the project’s existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100