toolisticon / toolisticon/kotlin-code-generation
Use Strategy/ProcessorList for filtered instances as well
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 2
- Forks
- 0
- Avg merge
- 3h 12m
- Merged PRs (30d)
- 5
Description
Current implementation only works for unbound strategies and processors, when filterIsInstance is applied, we continue with an generic list and use extension functions on those lists to execute the code.
Better: generalise the concept of value class lists and let filter return an instance of that new list type which does not need extension functions but provides executeAll/Single directly.
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
Start by reading the current Strategy/ProcessorList implementation and the filterIsInstance path, then trace the extension functions used to execute filtered lists. Done means filtered instances use a generalized value-class list that provides executeAll and executeSingle directly, rather than relying on generic-list extensions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100