Skip to content
This repository has been archived by the owner on May 11, 2021. It is now read-only.

🚨 REWRITE WARNING 🚨 #211

Open
Fuyukai opened this issue Dec 1, 2017 · 11 comments
Open

🚨 REWRITE WARNING 🚨 #211

Fuyukai opened this issue Dec 1, 2017 · 11 comments
Assignees

Comments

@Fuyukai
Copy link
Owner

Fuyukai commented Dec 1, 2017

The current codebase is bad. Awful, even.

So I'm rewriting most of it using Pyramid, and a more sane parsing setup. This parsing setup will be usable in other projects, since it'll be mostly independent from the rest of the code. This issue will track anything new or fancy that will come with the rewrite.

What will change:

  • Any self-hosted installs will explode as all the settings format change.
  • There will be a new ratelimit system based around queueing. Also, everything will be a lot faster. More to follow.

What won't change:

  • V3 data responses. I'll try to keep them consistent.
@Fuyukai Fuyukai self-assigned this Dec 1, 2017
@andrewzah
Copy link
Collaborator

😢

@dfreelan
Copy link

dfreelan commented Dec 7, 2017

sounds good!

I was hoping to reuse your code and translate it to something that can turn into either a Windows executable or even ideally run in a browser. But I was having a really hard time isolating the necessary components.

Maybe it'll be easier to do with the rewritten code :)

@morkenborken
Copy link

Any ETA on the rewrite? I'm working on a project that'll probably end up downloading a whole bunch of stuff with this so I'm wondering if it's worth waiting for.

@andrewzah
Copy link
Collaborator

The API from the user standpoint shouldn’t change too much even if we do rewrite it.

Not sure if the rewrite will happen or not, so I’d just go forward and use it as it is now.

@Fuyukai
Copy link
Owner Author

Fuyukai commented Feb 17, 2018

There's zero plan on changing the output of the API; programs working with it now will still work.

@morkenborken
Copy link

Thanks

@Fuyukai
Copy link
Owner Author

Fuyukai commented Jan 21, 2019

Like over a whole year later I have a real update on this. ETA: About a week or two. Unfortunately, due to cleanup of the parsing code this will require a version bump; I will add a transition period where v3 is routed to the old server and v4 is routed to the new one temporarily.

This will probably be the last major change to this project by me; only bugfixes and minor new parsing will be added after that. I'll continue to host the app until either OW dies or Blizzard finally blocks me.

@Js41637
Copy link
Contributor

Js41637 commented Jan 21, 2019

Good to hear. Overwatch is apparently a dying game anyway so won't be long now.

@andrewzah
Copy link
Collaborator

andrewzah commented Jan 21, 2019 via email

@jpylypiw
Copy link
Contributor

There is a unique selling point on this project, because there is no similar software at the moment.
Also it is fun to develop software many people use.

@Fuyukai
Copy link
Owner Author

Fuyukai commented Jan 21, 2019

I stopped playing back in late 2016, yeah. I'm continuing the maintainence despite that because parsing the website reliably is full of massive edge cases, and it's probably better for me to put that effort into it for everyone to use rather than have everyone make their own parsers which break on weird data.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants