PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Build price checking on historical or current data.
Nessuno ha ancora preso questa issue.
- Lingua principale
- Lua
- Stelle
- 5.4k
- Fork
- 2.4k
- Merge medio
- 1g 12h
- PR unite (30g)
- 26
Descrizione
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:
- Use a third party API (There is a project "poe-api-wrappers" which seems to be useful)
- 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
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
L’issue non indica file, test o punti di ingresso. Inizia individuando le aree di importazione delle build, visualizzazione degli oggetti e caricamento dei dati, quindi chiarisci se i prezzi provengono da un’API di terze parti o da dump di poe.ninja. Il lavoro sarebbe completo se consentisse di ottenere prezzi complessivi e per singolo oggetto stimati usando dati della lega attuali o storici.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- lua
- Ambito
- data, desktop
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100