OWAPI icon indicating copy to clipboard operation
OWAPI copied to clipboard

🚨 REWRITE WARNING 🚨

Open Fuyukai opened this issue 8 years ago • 11 comments

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 avatar Dec 01 '17 02:12 Fuyukai

😢

andrewzah avatar Dec 06 '17 00:12 andrewzah

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 :)

dfreelan avatar Dec 07 '17 21:12 dfreelan

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.

morkenborken avatar Feb 17 '18 03:02 morkenborken

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.

andrewzah avatar Feb 17 '18 03:02 andrewzah

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

Fuyukai avatar Feb 17 '18 11:02 Fuyukai

Thanks

morkenborken avatar Feb 19 '18 01:02 morkenborken

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.

Fuyukai avatar Jan 21 '19 09:01 Fuyukai

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

Js41637 avatar Jan 21 '19 09:01 Js41637

	I applaud the effort put into maintaining this. But why? I thought you stopped playing OW forever ago 
	
	

	

On Mon, Jan 21, 2019 at 6:50 PM +0900, "Js41637" [email protected] wrote:

OW is apparently a dying game anyway so won't be long now.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

andrewzah avatar Jan 21 '19 09:01 andrewzah

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.

jp1337 avatar Jan 21 '19 10:01 jp1337

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.

Fuyukai avatar Jan 21 '19 11:01 Fuyukai