PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Build price checking on historical or current data.

Abierto
#3,880 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

enhancement
Lenguaje dominante
Lua
Estrellas
5.4k
Forks
2.4k
Merge medio
1 d 12 h
PR fusionados (30 d)
26

Descripción

Check for duplicates
  • I've checked for duplicate issues by using the search function of the issue tracker
Is your feature request related to a problem?

I would like to suggest adding a way to see an estimated price on an imported build (overall & per item), to see a build price before starting it.
I feel searching for prices of gear on a build could rather be automated instead of the user searching one by one (sometimes for many builds)

Describe the solution you'd like

I was thinking how nice it would be to see an estimate of what a build could cost. At the very least the pricing on uniques (as they are a lot more consistent.)

I was thinking about this a bit and 2 ways I thought of that could be a good way to go is either:

  1. Use a third party API (There is a project "poe-api-wrappers" which seems to be useful)
  2. Give an option to import a dump file from a specific league (current or past) from the poe.ninja dumps.

The idea I had is to create a bit of space to the right of the item to display the price (depending on the method of getting the data as mentioned above).
And then just a drop down of ["day 1", "week 1", "week 2", "end of league / current"] (these dates could be the end of, as id end of week 1.)

The main reasoning behind this is so that users (especially newer) can have a better idea of the costs of a build, see if it could be a potentially viable league start or should rather be an ult.

Given there might be some issues with the logic (of mine) of the feature, but I have no problem brainstorm together.
But I do believe this to be a solid idea and would add major quality of life.

Describe alternatives you've considered

No response

Additional context

No response

Guía de contribución

Abrir la guía de contribución

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.

Línea de trabajo

El issue no nombra archivos, pruebas ni puntos de entrada. Empieza localizando las áreas de importación de builds, visualización de objetos y carga de datos, y luego aclara si los precios provienen de una API de terceros o de volcados de poe.ninja. Se consideraría terminado si permitiera obtener precios generales y por objeto estimados con datos de la liga actuales o históricos.

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

Evaluación

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

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.