Renaming required identifier changes require path
Open
Nobody has claimed this yet.
bug
check-syntax
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
Renaming a required identifier changes the module path in that file's require.
Example: two files, a.rkt and b.rkt
;; a.rkt
#lang racket
(provide a)
(define a 5)
;; b.rkt
#lang racket
(require "a.rkt")
(+ a 2)
Opening b.rkt, right clicking on a on line 3, and renaming it to foo changes the line 2 of b.rkt to (require foo).
What I expected: it would leave the require path alone.
Racket version: 8.1.0.7 [cs]
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue in DrRacket using the two-file a.rkt and b.rkt example, then inspect the rename operation triggered on a in b.rkt. Done means renaming the identifier changes its uses without changing the string path in the require form.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100