Delete dead read_more.js (replaced by truncated_text controller)

Open Beginner friendly
#7,305 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.

  • #7334 by @KoushikSagarr — open

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start by running the grep from the checklist to confirm nothing in app/ still uses js-read-more, js-read-less or js-full-text outside app/javascript/src/read_more.js and its test. The files involved are app/javascript/src/read_more.js, app/javascript/__tests__/read_more.test.js, and the require('./src/read_more') line in app/javascript/application.js. Done means those files are deleted and the require is removed, with npm run test and bin/lint passing.

Written by the indexing model from the issue text.

Description

Difficulty: Easy Good First Issue Help Wanted javascript

What

app/javascript/src/read_more.js toggles .js-read-more / .js-read-less links. No view renders those classes any more: the redesign replaced them with the truncated_text Stimulus controller (app/javascript/controllers/truncated_text_controller.js).

Checklist

  • Confirm grep -rn "js-read-more\|js-read-less\|js-full-text" app/ only matches read_more.js and its test
  • Delete app/javascript/src/read_more.js and app/javascript/__tests__/read_more.test.js
  • Remove require('./src/read_more') from app/javascript/application.js
  • 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.