Specs for deprecated methods
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 622
- Forks
- 402
- Avg merge
- 14h 51m
- Merged PRs (30d)
- 6
Description
There are some deprecated/obsolete methods like File.exists?, Thread#safe_level etc in the core library.
Looks like they aren't covered with tests there and moreover some existing specs were deleted recently - File.exists?, Dir.exists? and FileTest.exists?` (commit).
So I am wondering whether it is a well-considered decision or it's unintentional situation. I believe that as far as these methods are still available in MRI they should be a part of the specification.
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
Review the existing core library specs for deprecated methods such as File.exists?, Thread#safe_level, Dir.exists?, and FileTest.exists?, along with commit 79e4a3d7f5a2e81cefa824794ad82f704121dc7c. First determine whether the deleted specs were intentionally removed; done means reaching a decision about coverage for methods that remain available in MRI and adding or restoring the relevant specs if appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100