Open ReggiePark opened 1 month ago
1) Some users deliberately archive orders as a workaround for when azad gets stuck on them. 2) Getting stuck is a bug - there is no hiding from that - I've done a lot of work to allow azad to soldier on even if it has problems with a single order, but every now and then someone shows me a new way to break azad. 3) they sometimes don't want to wait for me to debug (or are not able to help me - if I had such a bug-triggering order in my history it stands to reason that I would fix it immediately - it'd be super easy!) 4) Archived orders are manually archived by their owners - it doesn't seem to be a process that Amazon inflicts on them automatically
Given the above, do we still think that going after archived orders is (on balance) beneficial?
First, let me say that I know what you are saying, I am a software developer myself...
However, as a user I would like to have the option to include archived orders. Since I only want to see orders that haven't been delivered yet I use it to hide every completed order over the last three month (the default orders view) and then 'clean up' the archived orders every now again by 'un-archiving' every thing that's older than 3 month. To use azad I'd have to un-archive all those orders, use it, and than archive them again.
Could you comment on this this?
It's from a closed issue: https://github.com/philipmulcahy/azad/issues/147
Just a note on this issue: As far as I understand from the code its not using any API but rather webscraping. The archived orders are just under a different URL but contain roughly the same layout as the unarchived orders.
Archived =
/gp/legacy/order-history?orderFilter=archived
Normal =/gp/css/order-history
Maybe it would be possible to support that after all?
Originally posted by @pke in https://github.com/philipmulcahy/azad/issues/147#issuecomment-2084573313