IQSS / IQSS/dataverse

Feature Request/Idea: Remove unused imports and methods

Open
#9,918 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: Code Infrastructure Feature: None Type: Suggestion User Role: Hackathon Participant
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request

Code that is never executed within Dataverse and that is unreachable from outside Dataverse should be removed. Unused imports should also be removed.

What kind of user is the feature intended for?
Developers

What inspired the request?
Many files in the codebase are messy and have low test coverage. But because of the messiness, it is hard to see what should be covered by tests.

This is also part of my all-time quest to improve the codebase, started a long time ago.

What existing behavior do you want changed?
No behaviour should change.

Any brand new behavior do you want to add to Dataverse?
No behaviour needs to be added.

Any open or closed issues related to this feature request?

  • #775 is the original code style issue
  • #9009 is an example that unused code can be removed
  • #9846 and #9847 should help keep up the quality by monitoring unused imports and methods

Contributor guide

Open the contributing guide

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.

Research direction

Start by reviewing the original code-style issue #775, the removal example in #9009, and the monitoring issues #9846 and #9847 to understand the intended scope. Done means unused imports and unreachable code are removed across the relevant Dataverse code without changing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.