Static state in SPI could lead to staleness issues
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 542
- Forks
- 101
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 2
Description
If you have a TypeProcessor that does stateful things, you could run into issues with that state remaining. Not sure if the static approach was intentional, but just mentioning.
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
Start by locating the SPI and TypeProcessor implementation and inspect how their state is created and retained. Reproduce whether a stateful TypeProcessor remains stale across processing runs, then determine the intended lifecycle. Done means the lifecycle is corrected or explicitly documented and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100