Delete dead emancipations.js (DataTable on a table that no longer exists)

Open Beginner friendly
#7,302 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@KoushikSagarr is already working on this.

Since Nov 2, 2026.

  • #7336 by @KoushikSagarr — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, jquery, rails, ruby
Domain
frontend

Research direction

The dead code is app/javascript/src/emancipations.js, which initializes a jQuery DataTable on table#all-case-emancipations; the comment at the top of app/views/emancipation_checklists/index.html.erb confirms that id is gone. Delete the file and its require('./src/emancipations') line in app/javascript/application.js. Done when /emancipation_checklists still loads as [email protected] and npm run test passes.

Written by the indexing model from the issue text.

Description

Difficulty: Easy Good First Issue Help Wanted javascript

What

app/javascript/src/emancipations.js starts a jQuery DataTable on table#all-case-emancipations. The redesigned app/views/emancipation_checklists/index.html.erb no longer renders that id (see the comment at the top of the view), so the script does nothing.

Checklist

  • Delete app/javascript/src/emancipations.js
  • Remove its require('./src/emancipations') line from app/javascript/application.js
  • Visit /emancipation_checklists as [email protected] and confirm the page still works
  • npm run test passes

Before you start

  • Comment here to be assigned. Setup is bin/setup, then bin/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

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rubyforgood/casa

All issues in rubyforgood/casa

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.