PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
Build price checking on historical or current data.
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Lua
- Sterne
- 5.4k
- Forks
- 2.4k
- Ø Merge
- 1 T. 12 Std.
- Gemergte PRs (30 T.)
- 26
Beschreibung
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
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Der Issue nennt keine Dateien, Tests oder Einstiegspunkte. Beginne damit, die Bereiche für Build-Import, Item-Anzeige und Datenladen zu lokalisieren, und kläre anschließend, ob die Preise aus einer Drittanbieter-API oder aus poe.ninja-Dumps stammen. Erledigt wäre die Aufgabe, wenn geschätzte Gesamt- und Einzelpreise mit aktuellen oder historischen Liga-Daten möglich wären.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- lua
- Bereich
- data, desktop
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100