objectionary / objectionary/lints
`long-live-object` lint is not implemented
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14
- Forks
- 39
- Avg merge
- 22h 54m
- Merged PRs (30d)
- 90
Description
How about we create a lint that would catch objects, located too far from their usages. In this program, f can be moved closer to its usage:
[] > app
foo 42 > f
… # some statements here
52.plus f > r
The lint should be able to accept maxObjectLifetime parameter. If its bigger than predefined threshold, the defect with warning severity should be generated.
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
No file, test, or entry point is named. Start by reading existing lint implementations and how they accept configuration parameters, then trace how object locations and usages are represented. Done means a long-live-object lint reports warning-severity defects when the configurable maxObjectLifetime threshold is exceeded, while recognizing the example’s movable object.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100