Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Recommendations 2.0

Abierto
  • ¿Algo no está bien?
#1,763 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
java
Área
backend

Línea de trabajo

Start by reading the current CH-based recommendation approach and the score analysis flow mentioned in the issue. Define the scope of the generic and reverse recommendation API, including plan inputs, candidate filtering, brute-force evaluation, and the number of results to return; the issue does not name files or tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

process/needs triage

Is your feature request related to a problem? Please describe.
The current way to do recommendations (recommended fit) is based on CH. We are seeing that this is often not sufficient and users are often deciding to implement their own Recommendation API.

It's also doesn't support "reverse recommendations", where we do not only recommend A->B but also B->A.
eg. vehicle routing, we currently recommend Vehicles for Visits, but we might want to also recommend Visits for Vehicles.

Describe the solution you'd like
We could implement a more generic approach where we are provided with a plan, a list of potential values (or a filter on the already provided plan) and then something which needs recommending. This could support Recommendations and Reverse Recommendations.

In an initial version, this could just be a Brute Force function, where:

  • we loop over all the options
  • run score analysis for each of them
  • return the best X results.

Most of the time, recommendations are only used with a nearly completed plan anyway, so the list of options is already minimal, but the filter could help to programmatically limit it further. We can look later to improve this.

Describe alternatives you've considered
The current CH approach doesn't do much better with this single assignment.

Lenguaje dominante
Java
Estrellas
1.8k
Forks
238
Merge medio
3 d 2 h
PR fusionados (30 d)
59

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TimefoldAI/timefold-solver

Todos los issues de TimefoldAI/timefold-solver

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.