Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gh 4581 remove jerven design mistakes #4582

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

JervenBolleman
Copy link
Contributor

GitHub issue resolved: #

Briefly describe the changes proposed in this PR:

Remove LimitedSize evaluation strategy code, as well as a few methods in the EvaluationStrategy API that was replaced by the collection factory API.

Closes #4581

@JervenBolleman JervenBolleman added the 🛠️ tech debt code refactoring, deprecation, and other technical debt tasks label May 21, 2023
@JervenBolleman JervenBolleman added this to the 5.0.0 milestone May 21, 2023
@JervenBolleman JervenBolleman self-assigned this May 21, 2023
@JervenBolleman JervenBolleman changed the base branch from main to develop May 21, 2023 20:03
@JervenBolleman JervenBolleman force-pushed the GH-4581-Remove-Jerven-Design-Mistakes branch from b12ed0f to 4b30d24 Compare April 26, 2024 14:28
As well as supplier methods later better done with the collection
factory API.

Signed-off-by: Jerven Bolleman <jerven.bolleman@sib.swiss>
@JervenBolleman JervenBolleman force-pushed the GH-4581-Remove-Jerven-Design-Mistakes branch from 4b30d24 to b241e9b Compare April 26, 2024 15:56
This allows to always be sure that we can fall back to disk if required.
Also allows optimized datastructures to be injected.

Signed-off-by: Jerven Bolleman <jerven.bolleman@sib.swiss>
@JervenBolleman JervenBolleman force-pushed the GH-4581-Remove-Jerven-Design-Mistakes branch from b241e9b to f8f7eee Compare April 26, 2024 16:45
@JervenBolleman
Copy link
Contributor Author

@hmottestad could this still be included in the next 5.x Milestone build?

@hmottestad
Copy link
Contributor

@hmottestad could this still be included in the next 5.x Milestone build?

Yeah. I haven't started on the build process yet. I saw you requested a review from me, so I'll take a look asap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛠️ tech debt code refactoring, deprecation, and other technical debt tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove my own design errors with v5
2 participants