Final step: remove jQuery, notifier.js and type_checker.js
Maintainers usually reply within 1 day
@1steve78 is already working on this.
Since Nov 14, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
This is the last step of the jQuery removal and is blocked by #7302 to #7316, so wait until those merge before starting. Delete app/javascript/src/notifier.js, app/javascript/src/type_checker.js, their Jest tests, and app/javascript/jQueryGlobalizer.js with its import. Remove jquery from package.json and the jQuery global from the Jest/standard config, and drop sweetalert2 from app/javascript/controllers/alert_controller.js only if nothing else uses it. Done when grep -rn '\$(\|jQuery' app/javascript returns nothing and npm run build, npm run test and bin/rails spec pass.
Written by the indexing model from the issue text.
Description
What
The last step of removing jQuery. Once the other sub-issues in #7301 are merged, delete the helpers that only exist for jQuery, then jQuery itself.
Blocked by: #7302–#7316 (see #7301).
Checklist
- Delete
app/javascript/src/notifier.js,app/javascript/src/type_checker.js,app/views/layouts/components/_notifier.html.erb(if unused) and their Jest tests - Delete
app/javascript/jQueryGlobalizer.jsand its import. Removejqueryfrompackage.json(including thejQueryglobal in the Jest/standard config) - If nothing imports
sweetalert2any more, remove it too (app/javascript/controllers/alert_controller.jsuses it today) -
grep -rn '\$(\|jQuery' app/javascriptreturns nothing.npm run build,npm run testandbin/rails specpass - Close #6685 (jQuery 4 upgrade) as no longer needed
Before you start
- Comment here to be assigned. Setup is
bin/setup, thenbin/dev. Logins are in the README. - JS tests:
npm run test. Lint:bin/lint. - Part of #7301 (removing jQuery). Keep this PR to just this file.
- Dominant language
- Ruby
- Stars
- 384
- Forks
- 558
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 63
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from rubyforgood/casa
-
⛓️ Security Difficulty: Easy Good First Issue Help Wanted ruby Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rubyforgood/casa#7404 ·
Maintainers usually reply within 1 day
-
Difficulty: Easy Good First Issue Help Wanted ruby Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rubyforgood/casa#7402 ·
Maintainers usually reply within 1 day
-
Remove the bin/bundle binstub (Heroku warns it can break Bundler on deploy)Possibly taken @Akash-Dhanwate claimed this 8 days ago. Opendependencies Difficulty: Easy Good First Issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
rubyforgood/casa#7325 · 2 comments ·
Maintainers usually reply within 1 day
-
Reports page: move export-button disable/re-enable into a Stimulus controllerMay be free again @Akash-Dhanwate claimed this 9 days ago, and no pull request is open. OpenDifficulty: Easy Good First Issue Help Wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rubyforgood/casa#7311 · 2 comments ·
Maintainers usually reply within 1 day
-
New case: use Stimulus for the "I don't know the court date yet" toggleMay be free again @Aryankn29 claimed this 9 days ago, and no pull request is open. OpenDifficulty: Easy Good First Issue Help Wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rubyforgood/casa#7310 · 1 comment ·
Maintainers usually reply within 1 day
All issues in rubyforgood/casa
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
internetee/registry#2984 ·
Maintainers usually reply within 6 days
-
Redis Lua error `@user_script:52: ERR value is not an integer or out of range` when `window_size` is configuredPossibly taken @mimosa claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
riscv/riscv-unified-db#2829 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
docker-library/ruby#534 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100