Closed cohenaj194 closed 2 weeks ago
The changes in this pull request enhance the alerting functionality and data handling within the auction system. In mega_alerts.py
, a new attribute, required_lvl
, is introduced for auction items, affecting how alerts are constructed and sent. The pull_single_realm_data
function now incorporates this attribute into alert messages. In utils/mega_data_setup.py
, the MegaData
class is updated to include required_lvl
in its data structures, ensuring it is validated and initialized correctly. These modifications improve the robustness and clarity of auction alerts and item level data.
File | Change Summary |
---|---|
mega_alerts.py | - Added handling for required_lvl in pull_single_realm_data , check_tertiary_stats_generic , and format_alert_messages . - Updated alert messages to include required_lvl when applicable. |
utils/mega_data_setup.py | - Introduced required_min_lvl and required_max_lvl in ilvl_info within __set_desired_ilvl , initialized to default values. - Updated snipe_info construction to include base_required_levels . - Modified method signatures to accept base_required_levels . |
.github/workflows/windows-exe-build.yml | - Updated AAA_VERSION from "1.2.4" to "1.2.5". |
AzerothAuctionAssassin.py | - Updated AAA_VERSION from "1.2.4.1" to "1.2.5". - Added code for dynamic import path adjustment for Windows C# binary execution. - Adjusted UI dimensions and labels for item level management. |
utils/api_requests.py | - Updated return signature of get_ilvl_items to include base_required_levels . |
AzerothAuctionAssassinData/example_desired_ilvl_list.json | - Added new item with ilvl 400 and required_min_lvl 71, required_max_lvl 79. - Duplicated entry for ilvl 483. |
Objective | Addressed | Explanation |
---|---|---|
Support required player levels in alerts (#139) | ✅ | |
Validate item level data with required levels (#139) | ✅ |
AzerothAuctionAssassin.py
include updates to item level processing logic, which may relate to the new required_lvl
attribute introduced in the main PR, as both involve item level management and enhancements in auction data handling.In the realm of auctions bright,
A new level shines with light.
Alerts now sing of levels due,
Withrequired_lvl
, we start anew.
Data dances, robust and clear,
Thanks to changes we hold dear! 🐇✨
Ill need to fix remove_ilvl_to_list
to handle the new feature, but we have to allow backwards compatibility too so this will work for people who dont have a required_lvl
set for anything in the AzerothAuctionAssassinData/desired_ilvl_list.json
@coderabbitai recommend a fix.
[
// cant remove
{
"ilvl": 400,
"buyout": 10000,
"sockets": false,
"speed": false,
"leech": false,
"avoidance": false,
"item_ids": [
1111
],
"required_lvl": 70
},
// can remove
{
"ilvl": 400,
"buyout": 1000,
"sockets": false,
"speed": true,
"leech": false,
"avoidance": false,
"item_ids": []
}
]
Failed conditions
10.6% Duplication on New Code (required ≤ 3%)
closes: https://github.com/ff14-advanced-market-search/AzerothAuctionAssassin/issues/139
Summary by CodeRabbit
Summary by CodeRabbit
New Features
required_lvl
, for auction items in alert messages.required_lvl
for item level information.get_ilvl_items
function to return required levels for items.Bug Fixes
required_min_lvl
andrequired_max_lvl
.Chores